Candidate Sourcing System

ABSTRACT

A computing system may be operable to store, in memory, a profile of a candidate, wherein the profile includes a résumé of the candidate. The computing system may be operable to associate, in memory, a electronically-readable identifier with the candidate profile. The computing system may be operable to read, via an electronic, the electronically-readable identifier from an article presented to the computing system. The computing system may be operable to locate the profile of the candidate in the electronic memory based on the read-in electronically-readable identifier. The computing system may be operable to retrieve the résumé of the candidate from the located profile. The computing system may be operable to present the résumé via a display of the computing system.

CLAIM OF PRIORITY

This patent application makes reference to, claims priority to andclaims benefit from:

-   U.S. Provisional Patent Application Ser. No. 61/683,496 entitled    “Method and System for Electronic Management of Recruiting” and    filed on Aug. 15, 2012; and-   U.S. Provisional Patent Application Ser. No. 61/674,258 entitled    “Method and System for Electronic Management of Recruiting” and    filed on Jul. 20, 2012.

Each of the above-identified applications is hereby incorporated hereinby reference in its entirety.

INCORPORATION BY REFERENCE

This patent application also makes reference to:

-   U.S. patent application Ser. No. 13/725,746 entitled “Method and    System for Electronic Management of Recruiting” and filed on Dec.    21, 2012, the entirety of which is hereby incorporated herein by    reference.

TECHNICAL FIELD

Aspects of the present application relate to recruiting management. Morespecifically, to a method and system for electronic management ofrecruiting.

BACKGROUND

Conventional methods and systems for managing recruiting processes canbe inefficient and inconvenient. Further limitations and disadvantagesof conventional and traditional approaches will become apparent to oneof skill in the art, through comparison of such approaches with someaspects of the present method and system set forth in the remainder ofthis disclosure with reference to the drawings.

BRIEF SUMMARY

A method and/or system is provided for electronic management ofrecruiting, substantially as illustrated by and/or described inconnection with at least one of the figures, as set forth morecompletely in the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts an example system for implementing electronic recruitingmanagement.

FIGS. 2A and 2B depict a state diagram illustrating operation of anexample recruiting terminal.

FIG. 3A depicts an example event schedule window displayed on arecruiting terminal.

FIG. 3B depicts an example event detail window displayed on a recruitingterminal.

FIG. 3C depicts an example candidate profile window displayed on arecruiting terminal.

FIG. 3D depicts an example candidate interactions window displayed on arecruiting terminal.

FIG. 3E depicts an example candidate documents window displayed on arecruiting terminal.

FIG. 3F depicts an example recruiter interactions window displayed on arecruiting terminal.

FIG. 3G depicts an example event wrap-up window displayed on arecruiting terminal.

FIG. 4A depicts an example candidate résumé/CV window displayed by anexample recruiting terminal.

FIG. 4B depicts an example candidate assessment overview windowdisplayed by an example recruiting terminal.

FIG. 4C depicts an example candidate completed assessment form windowdisplayed by an example recruiting terminal.

FIG. 4D depicts an example in-progress assessment form window displayedby an example recruiting terminal.

FIG. 4E depicts an example note-taking window displayed by an examplerecruiting terminal.

FIG. 4F depicts an example interview scheduling windows displayed on arecruiting terminal.

FIG. 4G depicts another example interview scheduling window displayed ona recruiting terminal.

FIGS. 5A-5C depict a flowchart illustrating an example process forat-event management of recruiting information.

FIG. 5D depicts a flowchart illustrating an example interview schedulingprocess.

FIG. 6 depicts components of an electronic recruiting management systemdeployed at a recruiting event.

FIG. 7A depicts a flowchart illustrating at-event candidate andrecruiter matchmaking using an electronic recruiting management system.

FIG. 7B depicts a flowchart illustrating at-event interview schedulingand coordination using an electronic recruiting management system.

FIG. 7C depicts a flowchart illustrating networking features of anelectronic recruiting management system.

FIG. 8A depicts an example public candidate profile window provided byan electronic recruiting management system.

FIG. 8B depicts an example public candidate activity window provided byan electronic recruiting management system.

FIG. 8C depicts an example public candidate projects window provided byan electronic recruiting management system.

FIG. 8D depicts an example private candidate home window provided by anelectronic recruiting management system.

FIG. 8E depicts an example private candidate discover window provided byan electronic recruiting management system.

FIG. 9A depicts an example public event profile window provided by anelectronic recruiting management system to a third party.

FIG. 9B depicts an example public event activity window provided by anelectronic recruiting management system to a third party.

FIG. 9C depicts an example event private profile administration windowprovided by an electronic recruiting management system.

FIG. 10A depicts an example public organization profile window providedby an electronic recruiting management system.

FIG. 10B depicts an example public organization activity window providedby an electronic recruiting management system.

FIG. 10C depicts an example recruiting dashboard window provided by anelectronic recruiting management system.

FIG. 10D depicts an example recruiter assessment window provided by anelectronic recruiting management system.

FIG. 10E depicts an example event assessment window provided by anelectronic recruiting management system.

FIG. 10F depicts an example event scheduler window provided by anelectronic recruiting management system.

FIG. 10G depicts an example requisition management window provided by anelectronic recruiting management system.

FIG. 10H depicts an example requisition creation window provided by anelectronic recruiting management system.

FIG. 10I depicts an example candidate and event discovery windowprovided by an electronic recruiting management system.

FIG. 11A depicts a flowchart illustrating an example process forcandidate pool management using an electronic recruiting managementsystem.

FIG. 11B depicts a flowchart illustrating an example process forcreating a job requisition using an electronic recruiting managementsystem.

FIG. 12 depicts a flowchart illustrating an example process for matchingcandidate and entities via an electronic recruiting management system.

FIG. 13 depicts a flowchart illustrating an example process forcandidate recommendations via an electronic recruiting managementsystem.

FIG. 14 depicts a flowchart illustrating an example process forcandidate relationship management via an electronic recruitingmanagement system.

FIG. 15 depicts an example recruiting management system that housesapplicant tracking systems for multiple organizations.

FIG. 16 depicts a flowchart illustrating an example process forprojecting recruiting-related information using an electronic recruitingmanagement system.

FIG. 17 depicts a flowchart illustrating an example process for matchingcandidates and requisitions over multiple organizations.

DETAILED DESCRIPTION

As utilized herein the terms “circuits” and “circuitry” refer tophysical electronic components (i.e. hardware) and any software and/orfirmware (“code”) which may configure the hardware, be executed by thehardware, and or otherwise be associated with the hardware. As usedherein, for example, a particular processor and memory may comprise afirst “circuit” when executing a first one or more lines of code and maycomprise a second “circuit” when executing a second one or more lines ofcode. As utilized herein, “and/or” means any one or more of the items inthe list joined by “and/or.” As an example, “x and/or y” means anyelement of the three-element set {(x), (y), (x, y)}. As another example,“x, y, and/or z” means any element of the seven-element set {(x), (y),(z), (x, y), (x, z), (y, z), (x, y, z)}. As utilized herein, the termsand “module” refer to functions than can be performed by one or morecircuits. As utilized herein, the terms “e.g.,” and “for example”set-off lists of one or more non-limiting examples, instances, orillustrations. As utilized herein, “list” is used generically todescribe arrangements of data such as lists, matrices, arrays, tables,etc. As utilized herein, a terminal, device, circuit, etc. is “operable”to perform a function whenever the circuitry comprises the necessaryhardware and code (if any is necessary) to perform the function,regardless of whether performance of the function is disabled, or notenabled, by some user-configurable setting.

FIG. 1 depicts an example system for implementing electronic recruitingmanagement. Referring to FIG. 1, the system comprises candidateterminals 102 a and 102 b, recruiter terminals 128 a and 128 b, and anetwork 113 to which the candidate terminals 102 and recruiter terminals128 are connected (and thus a part of).

The network 113 may comprise one or more servers 114 and one or morerouters, switches, cables, and/or other network “plumbing.” Theserver(s) 114 may comprise a processing circuit 120, a memory circuit122, and a networking circuit 118.

The processing circuit 120 may, for example, comprise one or more singleor multi-core central processing units (CPUs), application specificintegrated circuits (ASICs), and/or a field programmable gate arrays(FPGAs). The processing circuit 120 may be configured to effectuate theoperation of the server(s) in which it resides by executing lines ofcode stored in the corresponding one of the memory circuits 108 a-108 d.The lines of code may include an operating system and one or moreapplications. Examples of such applications include the databaseapplication 124 and the server application 126. One or more of theprocesses described below in this disclosure may result from such codebeing executed by the processing circuit 120.

The database application 124 may comprise code for managing recruitingdata stored in memory 122 and for generating a user interface via whichthe data may be stored to memory 122, retrieved from memory 122,organized, searched, and/or otherwise managed. The user interface may,for example, be served to candidate and/or recruiter terminals via theserver application 126. For example, database queries generated by therecruiting app 110, the browser 112, and/or the recruiting application130 may be relayed to the database application 124 via the serverapplication 126 and the results of the queries may be returned to theapp 110, the application 130, or the browser 112 via the serverapplication 126.

The server application 126 may comprise code for performing thefunctions of a web and/or application server. In this regard, theserver(s) 114 running the server application 126 may provide servicesand/or content to networked client devices, such as terminals 102 a, 102b, 128 a, and 128 b, via the use of one or more protocols (e.g., HTTP)and/or application programming interfaces (APIs).

The memory circuit 122 may, for example, comprise non-volatile memory,volatile memory, read only memory (ROM), random access memory (RAM),flash memory, magnetic storage, and/or any other suitable memory. Thememory circuit 122 may comprise program memory, run-time memory, andmass storage. Program memory may store lines of code executable by theprocessing circuit 120 to effectuate operation of the operating systemand one or more applications. Runtime memory may store data generatedand/or used during execution of the OS and/or applications. Mass storagemay store any number and/or types of data including candidate profiledata, organization profile data, documents, forms, and/or any other typeof data generated and/or used during recruiting processes. Data storedin mass storage may be managed via the database application 124.

The networking circuit 118 may comprise, for example one or more networkinterface cards (NICs) and may be configured to communicate over one ormore network links in accordance with one or more network protocols suchas, for example, Wi-Fi, LTE, wired Ethernet, DOCSIS, DSL, Fiber ChannelProtocol, and/or any other suitable protocol.

Each of the candidate terminals 102 a and 102 b, and each of therecruiter terminals 128 a and 128 b, comprises a respective one ofprocessing circuits 106 a-106 d, a respective one of networking circuits104 a-104 d, a respective one of user input devices 105 a-105 d, and arespective one of memory circuits 108 a-108 d. Each of the terminals 102a, 102 b, 128 a, and 128 b may be, for example, a portable terminal suchas a desktop PC or a mobile terminal such as a smartphone, a tabletcomputer, a notebook computer, or any other suitable computing device.)

Each of the processing circuits 106 a-106 d may, for example, comprise asingle or multi-core central processing unit (CPU), an applicationspecific integrated circuit (ASIC), and/or a field programmable gatearray (FPGA). Each of the processing circuits 106 a-106 d may beconfigured to effectuate operation of the terminal in which it residesby executing lines of code stored in the corresponding one of the memorycircuits 108 a-108 d. The lines of code may include an operating systemand one or more applications. Examples of such applications include therecruiting applications 110 a and 110 b, recruiting applications 130 aand 130 b, and the web browser applications 112 a-112 d. Processesdescribed below in the remainder of this disclosure may be the result ofsuch code being executed by one or more processing circuits 106 a-106 d.

Each of the memory circuits 108 a-108 d may, for example, comprisenon-volatile memory, volatile memory, read only memory (ROM), randomaccess memory (RAM), flash memory, magnetic storage, and/or any othersuitable memory. Each of the memory circuits 108 a-108 d may compriseprogram memory, run-time memory, and mass storage. Program memory maystore lines of code executable by the processing circuits 106 a-106 d toeffectuate operation of the operating system and one or moreapplications. Runtime memory may store data generated and/or used duringexecution of the OS and/or applications. Mass storage may store anynumber and/or types of data including candidate profile data,organization profile data, documents, forms, and/or any other type ofdata generated and/or used during recruiting processes.

Each of the networking circuits 104 a-104 d may be configured tocommunicate over one or more network links in accordance with one ormore network protocols such as, for example, Wi-Fi, LTE, wired Ethernet,DOCSIS, DSL, Fiber Channel Protocol, and/or any other suitable protocol.

The input devices 105 a-105 d may comprise, for example, a mouse, atouchpad, a motion sensor, a trackball, a voice recognition device, akeyboard, and/or any other suitable input device, with accompanyingcircuitry, that enables a user to interact with the respective terminal102 a, 102 b, 128 a, or 128 b.

Each of the instances 110 a and 110 b of the recruiting application 110may comprise code that, when executed, results in the performance of oneor more of the processes described in this disclosure. The process(es)may include, for example, providing a candidate-side user interface,processing of recruiting data, and/or communications among components ofthe recruiting system (e.g., via one or more web-based applicationprogramming interfaces). The process(es) may be performed by thecandidate terminal on which the code is executed, by the server(s) 114,by a recruiter terminal, and/or by a combination thereof.

Each of the instances 130 a and 130 b of the recruiting application 130may comprise code that, when executed, results in the performance of oneor more of the processes described in this disclosure. The process(es)may include, for example, providing an organization-side user interface,processing of recruiting data, and/or communications among components ofthe recruiting system (e.g., via one or more web-based applicationprogramming interfaces). The process(es) may be performed by therecruiter terminal on which the code is executed, by the server(s) 114,by a candidate terminal, and/or by a combination thereof.

Each of the instances 112 a-112 d of the web-browser application 112 maycomprise code that, when executed, enables accessing a web-basedinterface served by the server(s) 114. For example, the server(s) 114may serve an HTML and/or scripting language-based website that isaccessible via the web-browser application 112. Communications betweenthe web-browser 112 and the server(s) 114 may result in the performanceof one or more of the processes described in this disclosure. Theprocess(es) may include, for example, providing an organization-sideuser interface, providing a candidate-side user interface, processing ofrecruiting data, and/or communications among components of therecruiting system (e.g., via one or more web-based applicationprogramming interfaces). The process(es) may comprise client-sideprocesses (e.g., processes performed on the candidate or recruiterterminal by the web-browser 112 and/or its “plug-ins”) and/orserver-side processes (e.g., processes performed on the server(s) 114 bythe server application 126).

FIGS. 2A and 2B depict a state diagram illustrating operation of anexample recruiting terminal. For ease and clarity of description, thestate diagram is described in the context of a recruiter (“Recruiter”)acting on behalf of an organization (“Organization”) (e.g., an employer,a non-profit association, etc.) using the terminal 128 a at a recruitingevent (e.g., a job-fair, a membership drive, etc.) Although particularwindows are described as possessing particular interface elements fornavigating to particular other windows, the sequence in which thevarious states are accessible, the interface elements and/or informationavailable in any particular state, and the number of states are notlimited to example implementations disclosed herein.

The recruiting terminal 128 a may initialize to a state 202 in which alogin window is displayed. If Recruiter enters valid login credentialsthen the state of the terminal 128 b changes to a state 204 in which a“schedule” window is displayed. An example “schedule” window isdescribed below with reference to FIG. 3A.

While in the state 204, Recruiter may interact (e.g., by touching,clicking, typing in, etc.) with one or more interface elements (e.g.,buttons, sliders, drop-down menus, etc.) of the schedule window tonavigate to a state 206 in which a map function of the terminal 128 a islaunched. In the state 206, Recruiter may, for example, viewstreet-level maps and/or indoor maps of recruiting events.

While in the state 204, Recruiter may interact with one or moreinterface elements of the schedule window to navigate to a state 208 inwhich a “resources” (or “tools”) window is displayed. The resourceswindow may provide, for example, documents (e.g., digitally executablewaivers, confidentiality agreements, etc.), media (e.g., Organization'spromotional and/or orientation videos), and/or other information whichRecruiter may need or desire to access during the recruiting event. Forexample, a link to a document (e.g., a confidentiality agreement,waiver, etc.) requiring a candidate's signature may be provided in theresources window and, upon interacting with the link, the document maybe brought up for the candidate to review and for the candidate todigitally sign (e.g., write a signature with a stylus on a touchscreen,provide a finger print via an optical reader, take a picture of his/herface, type in a private-key, etc.). The documents, media, and/or otherresources available may be specific to Organization, Recruiter, and/orthe particular event. That is, different resources may be availabledepending on the organization, the event, and/or the recruiter logged-into the terminal 128 a.

While in the state 204, Recruiter may interact with one or moreinterface elements of the schedule window to navigate to the state 212in which an “event wrap-up” window is displayed. An example eventwrap-up window is described below with reference to FIG. 3G.

While in the state 204, Recruiter may interact with one or moreinterface elements of the schedule window to navigate to the state 214in which an “event detail” window is displayed. An example event detailwindow is described below with reference to FIG. 3B.

While in the state 204, Recruiter may interact with one or moreinterface elements of the schedule window to navigate to state 216 inwhich a “reminders” window is displayed. The reminders window maydisplay a task list and/or calendar view of upcoming recruiting-relatedevents, appointments, deadlines, etc. Via interface elements of thereminders window, Recruiter may be enabled to view, sort, filter, set,clear, and/or otherwise manage reminders.

While in the state 204, Recruiter may interact with one or moreinterface elements of the schedule window to navigate to state 218 inwhich an “interactions list” window may be displayed. An exampleinteractions list window is described below with reference to FIG. 3F.

While in the state 212, Recruiter may interact with one or moreinterface elements of the wrap-up window to navigate to state 210 inwhich an “event feedback” window is displayed. The event feedback windowmay provide fillable forms, surveys, and/or other user interfaceelements for collecting information about the recruiting event from therecruiters who attended the event. Such information may be stored (e.g.,in memory 108 and/or memory 122) for later generating various eventand/or recruiting-related metrics (e.g., to assess Recruiterperformance, cost-effectiveness of recruiting processes, etc.)

While in the state 212, Recruiter may interact with one or moreinterface elements of the wrap-up window to navigate to state 220 inwhich an “expense report” window is displayed. The expense report windowmay provide fillable forms and/or other user interface elements forcollecting expense reports to enable reimbursement as well analysis andmanagement of recruiting budgets, cost-effectiveness, etc.

While in the state 214, Recruiter may interact with one or moreinterface elements of the event detail window to navigate to state 232in which a “candidate list” window is displayed. An example candidatelist window is described below with reference to FIGS. 4A and 4B.

While in the state 214, Recruiter may interact with one or moreinterface elements of the event detail window to navigate to state 222in which a candidate profile window is displayed. An example candidateprofile window is described below with reference to FIG. 3C.

While in the state 218, Recruiter may interact with one or moreinterface elements of the interactions list window to navigate to state228 in which an “interaction details” window is displayed. Interfaceelements of the interactions detail window may enable Recruiter to viewand/or edit (e.g., add contact information, a photo, type a note, etc.)past interactions with one or more people (e.g., candidates, otherrecruiters, organization members/employees, etc.).

While in the state 222, Recruiter may interact with one or moreinterface elements of the candidate profile window to navigate to state224 in which a “candidate documents” window is displayed. An examplecandidate documents window is described below with reference to FIG. 3E.

While in the state 222, Recruiter may interact with one or moreinterface elements of the candidate profile window to navigate to state226 in which a “candidate interactions” window is displayed. An examplecandidate interactions window is described below with reference to FIG.3D.

While in the state 232, Recruiter may interact with one or moreinterface elements of the candidate list window to navigate to state 230in which a candidate scan/search window is displayed. While in state230, the terminal 128 a may be configured to scan (e.g., optically reada QR code, wirelessly read an RFID tag, and/or receive a wirelesssignature) a candidate terminal (e.g., terminal 102 a) to recover aunique identifier, and then search a database of candidates (e.g.,stored in memory 108 and/or memory 122) for a candidate associated withthe unique identifier. Additionally or alternatively, Recruiter canmanually enter candidate information and search for a database recordmatching the entered information. If a matching record is found, thestate of the terminal 128 a proceeds to state 236 in which a “candidaterésumé/CV window” is displayed, but if no matching record is found, thestate of the terminal returns to state 232.

While in the state 232, Recruiter may interact with one or moreinterface elements of the candidate list window to manually select acandidate (“Candidate”) from the list. Upon selection of Candidate thestate of the terminal 128 a proceeds to state 236 in which a “candidaterésumé/CV window” is displayed. An example candidate résumé/CV window isdescribed below with reference to FIG. 4A.

While in the state 232, Recruiter may interact with one or moreinterface elements of the candidate list window to navigate to state 234in which an “add candidate” window is displayed. Interface elements ofthe add candidate window may enable entering candidate information toadd a new candidate to the list of candidates. Upon completion ofentering the candidate information, the state of the terminal 128 a mayreturn to the state 232.

While in the state 236, Recruiter may interact with one or moreinterface elements of the résumé/CV window to navigate to state 240 inwhich a “résumé/CV capture/add” window is displayed. While in the state240, the Recruiter may be enabled to obtain Candidate's résumé/CV andsave the résumé/CV to memory such that it is associated with Candidatein memory. The résumé/CV may be obtained by, for example, scanning apaper copy, taking a photo of a paper copy, receiving it via a wired orwireless connection to a candidate terminal, and/or downloading it fromthe server(s) 114 and/or another web-host.

While in the state 236, Recruiter may interact with one or moreinterface elements of the résumé/CV window to navigate to state 238 inwhich a “schedule interview(s)” window is displayed. Example scheduleinterview windows are described below with reference to FIGS. 4F and 4G.

While in the state 236, Recruiter may interact with one or moreinterface elements of the résumé/CV window to navigate to state 244 inwhich a “scratchpad” window is displayed. An example scratchpad windowis described below with reference to FIG. 4E.

While in the state 236, Recruiter may interact with one or moreinterface elements of the résumé/CV window to navigate to state 242 inwhich an “assessments list” window is displayed. An example assessmentslist window is described below with reference to FIG. 4B.

While in the state 242, Recruiter may interact with one or moreinterface elements of the résumé/CV window to navigate to state 248 inwhich a “view assessment detail” window is displayed. An example viewassessment detail window is described below with reference to FIG. 4C.

While in the state 242, Recruiter may interact with one or moreinterface elements of the résumé/CV window to navigate to state 248 inwhich a “fill assessment” window is displayed. An example fillassessment window is described below with reference to FIG. 4D.

FIG. 3A depicts an example event schedule window displayed on arecruiting terminal. For ease and clarity of description, it is assumedthe event schedule window 300 is being displayed on the terminal 128 a.

The interface elements 310, 311, 312, and 313 enable navigating betweenthe scheduling window (FIG. 3A), a map window, an interactions listwindow (FIG. 3F), and a resources window.

Selection of the interface element 303 (e.g., as a result of beingclicked with a mouse or tapped on a touchscreen) may bring up areminders window. The reminders window may, in turn, display a task listand/or calendar view of upcoming recruiting-related events,appointments, deadlines, etc., and may enable viewing, sorting,filtering, setting, clearing, and/or otherwise managing reminders.

Selection of the interface element 304 may bring up an event wrap-upwindow such as the one described below with reference to FIG. 3G. Theinterface element 304 comprises a numerical field 308 indicating howmany events are waiting to be wrapped-up by the user of the terminal 128a.

The interface elements 301 a-301 d may each correspond to a filter to beapplied to the list of events to determine which events are displayed inthe list. In the example implementation, the filters include: nearbyevents (e.g., based on GNSS coordinates and/or other locationinformation), today's events, upcoming events, and all events. Theunderlying data records used to populate the list may be stored in localmemory 108 c and/or in the memory 122 of the server(s) 114.

Each of the elements 301 a-301 d comprises a respective one of numericalfields 302 a-302 d, where the numerical fields give a preview of howmany events correspond to such a filter. The numbers shown are arbitraryfor ease and clarity of description, and not intended to be limiting. Inthe example scenario depicted, element 301 c is selected (as indicatedby the heavy line), and six upcoming events (each corresponding to oneof the list entries 307 ₁-307 ₆) are displayed in the list.

Each of the list entries 307 ₁-307 ₆ corresponds to an event that meetsthe currently-selected filter criteria (“upcoming events” in thescenario depicted). Each of list entries 307 _(i) (i being an integerbetween 1 and 6) comprises interface elements 305 _(i) and 306 _(i).

Selection of the interface element 305 _(i), may cause candidateprofiles, resources, and/or other data associated with the event i to bedownloaded to the terminal 128 a from the server(s) 114. In this manner,any and/or all data needed for an event may be stored locally on theterminal 128 a for offline access. Where memory on the terminal 128 a islimited and/or where the terminal 128 a is guaranteed network access forthe duration of the event, such downloading may be unnecessary and/orundesirable. Where the terminal 128 a does operate in an offline mode,data in the memory 108 c and data in the memory 122 may be occasionally(e.g., upon establishment of a network connection and/or upon request)and/or periodically be synchronized such that data on both the terminal128 a and the server(s) 114 remains up-to-date to the extent possibleand/or desired. Maintaining the data on the server(s) 114 up-to-date mayenable other recruiting terminals and/or candidate terminals to accessthe data at or near real-time (where such other terminals have theappropriate permissions to access such data).

Selection of the interface element 309 may bring up a calendar windowwhich may contain the logged-in user's calendar information, calendarinformation for other members of the entity for which the logged-in useris recruiting, calendar information for candidates, etc. The calendarwindow may be similar to, link to, or be a sub, or superset of, theinterview scheduling window described below with reference to FIGS. 4Fand 4G.

Selection of the interface element 306 _(i) may bring up an eventdetails window such as shown in FIG. 3B.

FIG. 3B depicts an example event detail window displayed on a recruitingterminal. In FIG. 3B there is shown an event details window 319. Forease and clarity of description, it is assumed that the window 319 isbeing displayed in response to selection, by Recruiter, of the interfaceelement 306 ₂ (FIG. 3A) corresponding to Event 2.

The interface element 314 is a profile picture for Event 2. The picturemay, for example, have been selected by an event coordinator via anevent administration interface. The interface element 315 may comprise abrief description of Event 2. For example, the interface element 315 maycomprise the name, date, and location of Event 2.

Selection of the interface element 316 may bring up a candidate listwindow such as shown in FIG. 4A.

Each of the interface elements 318 ₁-318 _(M) (M being an arbitraryinteger) may be generated from underlying candidate data records storedin local memory 108 c and/or in the memory 122 of the server(s) 114.Each of the interface elements 318 ₁-318 _(M) corresponds to a candidatewho meets the selected filtering criteria established via interfaceelement 317. Thus, in the scenario depicted, M candidates meet thecurrent filtering criteria. The elements 318 ₁-318 _(M) may be sortedby, for example, a cultural fit score (discussed in more detail below)and/or by any other field of information in the underlying data recordsstored in memory. As an example, interface element 317 may enablefiltering by: candidates who registered for Event 2; candidates whoattended, or are in attendance, at Event 2; candidates who have beenseen by Recruiter or another recruiter working for Organization; andcandidates who, after being screened, have been invited for furtherscreening/interviewing with Organization.

Each element 318 _(m) (m being an integer between 1 and M) may comprisea caption that provides quick-glance information (e.g., name, collegemajor, cultural fit with Organization, and/or any other suitableinformation) that may inform Recruiter as to which candidate is which.Selection of the element 318 _(m) may bring up the candidate profilewindow 329 shown in FIG. 3C.

FIG. 3C depicts an example candidate profile window displayed on arecruiting terminal. The candidate profile window 329 comprisesinterface elements 320-328. For ease and clarity of description, it isassumed that the window 329 is being displayed in response to selection,by Recruiter, of the interface element 318 ₂ (FIG. 3B) corresponding toCandidate 2 by Recruiter.

The interface element 320 is a profile picture for Candidate 2. Thepicture may, for example, have been uploaded by Candidate 2 or taken ofCandidate 2 at Event 2 or a previous event.

The interface element 322 may comprise a biography of Candidate 2. Thebiography may, for example, have been uploaded to the server(s) 114 byCandidate 2 prior to Event 2 and/or scanned or typed into a registrationterminal at Event 2.

The interface element 323 may comprise one or more scores that indicatea compatibility between Candidate 2 and Organization, between Candidate2 and one or more of Organization's open requisitions (e.g., open jobswithin an Employer and/or positions within an association), and/orbetween Candidate 2 and Recruiter. In an example implementation, thescore(s) may be based on a cultural fit, as described in more detailbelow with reference to, for example, FIG. 12.

Selection of the interface element 324 may bring up an online profile ofCandidate 2. An example online profile is described below with referenceto FIGS. 8A and 8B.

The interface element 321 may comprise contact info for Candidate 2.Selection of information in the interface element 321 may bring up anappropriate application for contacting Candidate 2. For example, inresponse to selection of an email link in the interface element 321, ane-mail app may open on the recruiting terminal. As another example,selection of a “messaging” link in the interface element 321, amessaging window may appear in which Recruiter can enter the message.Clicking “send” may then, for example, cause the message to be deliveredvia a method selected by Candidate 2. Example methods include email,SMS, and a messaging component of Candidate 2's online profile.

The interface elements 326, 327, and 328 provide for navigating betweenthe window 329 of FIG. 3C, the window 337 of FIG. 3D, and window 339 ofFIG. 3E.

FIG. 3D depicts an example candidate interactions window displayed on arecruiting terminal. The candidate interactions window 337 comprisesinterface elements 330 ₁-330 ₃, 331 ₁-331 ₃, 332, and 325 in addition topreviously-discussed interface elements 326-328. For ease and clarity ofdescription, it is assumed that the window 337 is being displayed inresponse to selection, by Recruiter, of the interface element 327 in thewindow 329 of FIG. 3C.

Each of the interface elements 330 ₁-330 ₃ (where three is an arbitrarynumber chosen for ease and clarity of description and not intended to belimiting) corresponds to an interaction with Candidate 2. An interactioncould be, for example, a formal or informal meeting, an interview, aphone call, an email, etc.

Each of the interface elements 330 ₁-330 ₃ comprises a caption thatprovides at-a-glance information (e.g., date and location) to aidRecruiter in determining which interaction is which. Each interfaceelements 330 _(i) (i being an integer between 1 and 3, in the depictedexample) comprises an interface element 331 _(i) selection of whichbrings up an interaction details window which may provide more in-depthinformation about interaction i with candidate 2. Such information may,for example, include: Candidate 2 profile information, recruiting eventprofile information if interaction i was a recruiting event, a map ofthe location of interaction i, and notes taken during interaction i byRecruiter or whichever agent of Organization interacted with Candidate 2during interaction i.

Each of the interface elements 330 ₁-330 ₃ may be generated fromcandidate data records stored in the memory 108 c and/or the memory 122.The interactions data may have been manually entered by a user of arecruiting terminal or other computing device and/or may have beenautomatically generated. Automatic generation of an interaction mayoccur, for example, in response to a recruiting terminal coming within acertain distance (e.g., Bluetooth range, Wi-Fi range, an NFC tap, etc.)of a candidate terminal associated with Candidate 2.

Selection of the interface element 332 may bring up a window for manualentry of a new interaction with Candidate 2.

Selection of the interface element 325 may bring up a window for sendinga message (e.g., email, SMS, inter-profile message, etc.) to thecandidate. Information about the previous interactions with thecandidate may be automatically included, or suggested for inclusion, inthe message to refresh the candidate's memory as to the identity of themessage sender. Additionally or alternatively, the candidate's messagingclient may automatically search the candidate's interactions uponreceiving the message and display interactions with the message senderalongside the message (e.g., where the sender is a recruiter, the dateand location that candidate met with the recruiter may be presented tothe candidate along with the message).

FIG. 3E depicts an example candidate documents window displayed on arecruiting terminal. The candidate documents window 339 comprisesinterface elements 334 ₁-334 ₂, 335 ₁-335 ₂, and 336 ₁-336 ₂ in additionto previously-discussed interface elements 326-328. Although twoinstances of each of the elements 334, 335, and 336 are shown, anynumber of instances may be present. For ease and clarity of description,it is assumed that the window 339 is being displayed in response toselection, by Recruiter, of the interface element 328 in the window 329of FIG. 3C.

Selection of the interface element 334 _(i) (where i is an integerbetween 1 and 2) may bring up a window in which a corresponding one ofCandidate 2's résumé/CV is displayed (e.g., as a text file or as a.pdf). The different versions of Candidate 2's résumé/CV may correspond,for example, to different times and/or to different requisitions orposition sought.

Selection of the interface element 334 _(i) (where i is an integerbetween 1 and 2) may bring up a window in which a corresponding one ofCandidate 2's publications is displayed (e.g., as a text file or as a.pdf).

Selection of the interface element 336 _(i) (where i is an integerbetween 1 and 2) may bring up a window in which a corresponding one ofCandidate 2's forms is displayed (e.g., as a text file or as a .pdf).One or more of the forms may be, for example, a waiver, aconfidentiality agreement, or some other document executed by Candidate2 and scanned into the electronic recruiting system. Additionally oralternatively, one or more of the forms may be an assessment form, aperformance review, a note, or some other document pertaining tocandidate 2 generated by Recruiter and/or another agent of Organization.

FIG. 3F depicts an example recruiter interactions window displayed on arecruiting terminal. The window 346 shown in FIG. 3F comprises interfaceelements 340, 341 ₁-341 ₄, 342 ₁-342 ₄, and 343. For ease and clarity ofdescription, it is assumed that the window 346 is being displayed inresponse to selection, by Recruiter, of the interface element 312 in thewindow 300 of FIG. 3A. The window 246 is similar to the window 337 ofFIG. 3D, with the exception that the window 246 lists interactions thatspecific to Recruiter but not specific to any particular candidate.

Each interface element 341 _(i) (where i an integer between 1 and 4 and4 was arbitrarily chosen for ease and clarity of description) may besimilar to one of the interface elements 330 ₁-330 ₃. Each interfaceelement 342 _(i) (where i an integer between 1 and 4 and 4 wasarbitrarily chosen for ease and clarity of description) may be similarto one of the interface elements 331 ₁-331 ₃. Each interface element 344_(i) (where i an integer between 1 and 4 and 4 was arbitrarily chosenfor ease and clarity of description) may be similar the interfaceelement 325. The interface element 343 may be similar to the interfaceelement 332.

FIG. 3G depicts an example event wrap-up window displayed on arecruiting terminal. The window 347 shown in FIG. 3G comprises interfaceelements 345 ₁-345 ₂, 346 ₁-346 ₂, and 348 ₁-348 ₂ (two instances ofeach are shown for ease and clarity of description and the number ofinstances is not limited). For ease and clarity of description, it isassumed that the window 347 is being displayed in response to selection,by Recruiter, of the interface element 304 in the window 300 of FIG. 3A.

Each of the interface elements 345 ₁ and 345 ₂ correspond to an event tobe wrapped-up. Selection of the interface element 346 _(i) (where i isan integer between 1 and 2 in the depicted example) may bring up awindow in which Recruiter can enter feedback about the correspondingevent. Such feedback may be in the form of, for example, aquestionnaire. Selection of the interface element 348 _(i) (where i isan integer between 1 and 2 in the depicted example) may bring up awindow in which Recruiter can enter an expense report for thecorresponding event. By digitally capturing the expense reportinformation, budgeting may be performed in, or near, real-time, andmetrics such as cost-effectiveness of events may be analyzed.

Any of the windows described with reference to FIGS. 3A-3G may, forexample, be populated by pulling the underlying information from thedatabase(s) 124 via an API.

FIG. 4A depicts an example candidate résumé/CV window displayed on arecruiting terminal. For ease and clarity of description, it is assumedthat the window 400 is being displayed in response to selection, byRecruiter, of the interface element 316 in the window 319 of FIG. 3B.

Selection of the interface element 402 may return the terminal 128 a tothe window 319 of FIG. 3B.

Each of the interface elements 405 ₁-405 ₅ may be generated fromunderlying candidate data records stored in local memory 108 c and/or inthe memory 122 of the server(s) 114. Each of the interface elements 405₁-405 ₅ corresponds to a candidate who is associated with Event 2 andthat meets the selected filtering criteria established using interfaceelement 403. Thus, in the scenario depicted, five candidates meet thecurrent filtering criteria (where five was arbitrarily selected for easeand clarity of description and is not intended to be limiting). Theelements 405 ₁-405 ₅ may be sorted by, for example, a cultural fit score(discussed in more detail below) and/or by any other field ofinformation in the underlying data records stored in memory. As anexample, interface element 403 may enable filtering by: candidates whoregistered for Event 2; candidates who attended, or are in attendance,at Event 2; candidates who have been seen by Recruiter or anotherrecruiter working for Organization; and candidates who, after beingscreened, have been invited for further screening/interviewing withOrganization.

Selection of the interface element 402 may bring up a window which mayenable searching for a particular candidate among the list of candidatescorresponding to elements 405 ₁-405 ₅. The search may be performed basedon a unique identifier of the particular candidate which may be manuallyentered by Recruiter (e.g., a name, mobile phone number, email address,etc.) and/or may be entered via an electronic scanning or reading of anarticle associated with the particular candidate. For example, a barcodeor QR code uniquely associated with the particular candidate may be readfrom the candidate's badge or smartphone. As another example, a uniqueID may be read via Bluetooth, Wi-Fi, NFC, USB, and/or any other suitablecommunication protocol.

Selection of the interface element 406 may bring up a window via which acandidate can be manually entered (e.g., after not being found via asearch/scan).

The interface element 407 may display Candidate 2's résumé/CV (e.g., asa text file or .pdf). Selection of the interface element 408 may bringup a window for adding a résumé/CV for Candidate 2 to the system (e.g. asecond résumé/CV tailored for different field or position). Therésumé/CV may be added by, for example, scanning a paper copy or takinga picture of a paper copy with a camera of the terminal 128 a.

The interface elements 409, 410, 411, and 412 enable navigating betweenthe window 400 (FIG. 4A), an assessments window (FIG. 4B), a scratch padwindow (FIG. 4E), and a schedule interview window (FIGS. 4F and 4G).

FIG. 4B depicts an example candidate assessment overview windowdisplayed on a recruiting terminal. For ease and clarity of description,it is assumed that the window 401 is being displayed in response toselection, by Recruiter, of the interface element 410 in the window 400of FIG. 4A.

The interface element 417 may provide a composite score (e.g.,aggregate, mean, and/or median score) for the candidate based on aplurality of previously-completed assessments of the candidate. In anexample implementation, a side-by-side comparison of such assessments(e.g., from various recruiters) used in generating the composite scoremay be viewable on the terminal 128 a.

Each of the interface elements 419 ₁-419 ₃ (where the number ofinstances was arbitrarily chosen as three for ease and clarity ofdescription and is not intended to be limiting) corresponds to acompleted or ongoing assessment of Candidate 2. Each of the assessmentforms may have been completed, or may be in the process of beingcompleted, by Recruiter and/or by another member of Organization (wherethe proper permissions are in place for Recruiter to view suchassessment forms). Example assessment forms are described below withrespect to FIGS. 4C and 4D.

Each of the interface elements 419 ₁-419 ₃ comprises a caption thatprovides at-a-glance information (e.g., assessor, date, and location) toaid Recruiter in determining which assessment form is which. Eachinterface elements 419 _(i) (i being an integer between 1 and 3)comprises an interface element 418 _(i), selection of which brings up anassessment form window such as described below with respect to FIG. 4C.

The interface element 416 may enable selection of criteria for filteringand/or sorting the assessment forms listed in the window 401. Forexample, assessment forms may be filtered by date, by assessor, etc.

Each of the interface elements 421 ₁ and 421 ₂ (where the number ofinstances was arbitrarily chosen as two for ease and convenience ofdescription and is not intended to be limiting) may bring up anassessment form such as the one described below with reference to FIG.4D. Where there are multiple instances of the interface element 421, asin FIG. 4B, each form may correspond to a different assessment form,where different forms may be customized for differentrequisitions/positions, for different recruiters, for differentcandidates, and/or for different recruiting events.

FIG. 4C depicts an example completed assessment form displayed on arecruiting terminal. The form comprises a caption 430, assessment fields423 ₁ and 423 ₂, 425 ₁ and 425 ₂, and 427 ₁ and 427 ₂, and an interfaceelement 429 for bringing up a note-taking window such as the onedescribed below with reference to FIG. 4E. For ease and clarity ofdescription, it is assumed that the assessment form is being displayedin response to selection, by Recruiter, of the interface element 419 ₂in the window 401 of FIG. 4B and that the assessment form was completedby Assessor.

The caption 430 may comprise information such as Assessor's name,Candidate 2's name, the date of the assessment, the purpose of theassessment (e.g., the requisition/position for which candidate was beingconsidered), etc.

Each of the assessment fields 423 ₁ and 423 ₂ (where the number ofinstances was arbitrarily chosen as two for ease and convenience ofdescription and is not intended to be limiting) may comprise a questionasked of Candidate 2 and Assessor's assessment (e.g., in the form anumerical rating from, for example, 1 to 5) of Candidate 2's response tothat question.

Each of the assessment fields 425 ₁ and 425 ₂ (where the number ofinstances was arbitrarily chosen as two for ease and convenience ofdescription and is not intended to be limiting) may comprise a questionasked of Candidate 2 and Candidate 2's response to the question. Thecandidate's response may be, for example, typed in by Assessor duringdiscussion with Candidate 2, typed in by Candidate 2 (on the recruiterterminal 128 a and/or on a candidate terminal and subsequentlycommunicated to the recruiter terminal 128 a), and/or recorded via amicrophone of the recruiter terminal 128 a.

Each of the assessment fields 427 ₁ and 427 ₂ (where the number ofinstances was arbitrarily chosen as two for ease and convenience ofdescription and is not intended to be limiting) may comprise acharacteristic (e.g., good leadership, motivated, good time management,outgoing, well-spoken, etc.) and the assessor's assessment (e.g., in theform a numerical rating from, for example, 1 to 5) of the extent towhich the candidate possesses such characteristic.

Each of the questions/characteristics in fields 423 ₁, 423 ₂, 427 ₁, 427₂, and 429 may have been selected from a repository of questions eithermanually by Assessor and/or algorithmically by the terminal 128 a and/orserver(s) 114 based on various parameters. Example parameters include: aprofile of Candidate 2, a profile of Assessor, the requisition/positionfor which Candidate 2 was assessed, the event at which Candidate 2 wasassessed, previously-selected questions/characteristics (in this formand/or in a previous form), and/or answers/assessments to/of previousquestions/characteristics (in this form or in a previous form).Information on which the question/characteristic selection was based maybe sourced from a profile of Candidate 2 and/or another candidate'sprofile, a profile of Organization and/or another organization'sprofile, and/or a profile of the event at which the assessment form wascompleted. Examples of information found in such profiles are describedbelow with reference to FIGS. 8A, 8B, 9A, 9B, 10A and 10B.

The repository of questions and characteristics from which the questionsand characteristics are selected may be questions generated by theassessor and/or other assessors within the Organization. For example,when an assessor generates a new question for a form, that question maybe stored into the repository and the assessor may be prompted to entercontext information about who, what, where, when, why, and/or how thequestion/characteristic is being used. In this manner, a sharing (e.g.,intra and/or inter-organization sharing, depending on permissions) ofassessment questions/characteristics and context information about thosequestions/characteristics (e.g., perceived merits, deficiencies,recommended use scenarios, etc.) may be enabled by the electronicrecruiting system. Such sharing may lead to highly-customized candidateassessments that are more effective and efficient in identifying thebest candidates.

Also, the assessment questions/characteristics may be assessed todetermine their effectiveness (and deleted, refined, etc., asnecessary). For example, after using a particularquestion/characteristic in assessing a candidate, Recruiter may beprompted (e.g., via a message to Recruiter's profile in the electronicrecruiting system) to provide feedback on whether Recruiter believed thequestion/characteristics to be effective in determining whether thecandidate was a good fit. As another example, when a candidate assessedbased on a particular question/characteristic is subsequently hired, theeffectiveness of that particular question/characteristic may be assessedbased on the candidate's subsequent performance reviews.

FIG. 4D depicts an example in-progress assessment form displayed on arecruiting terminal. The assessment form shown in FIG. 4D is similar tothe assessment form in FIG. 4C except that the form in FIG. 4D is notyet completed. That is, by interacting with the interface elements 433₁, 433 ₂, 435 ₁, 435 ₂, 437 ₁, and 437 ₂, Recruiter can fill-in his/herassessment of Candidate 2.

As discussed above, the questions/characteristics of the form shown inFIG. 4D may be customized for this particular assessment of thisparticular candidate (Candidate 2) by this particular assessor(Recruiter). The customization may have been prior to Recruiterselecting (in Window 401) the form and/or may occur during completion ofthe form. The questions/characteristics may have been selected based on,for example, the field in which Candidate 2 is seeking a position,Candidate 2's cultural fit with Organization, Candidate 2's pastexperience, Candidate 2's purported skills or expertise, Recruiterstechnical and/or employment background, and/or any characteristics ofRecruiter, Candidate, and/or Organization deemed applicable to effectiveassessment. Where the questions/characteristics are dynamically selectedduring completion of the form, a subsequent question may be selected ona previous question and/or response/assessment provided for a previousquestion/characteristic. For example, question 432 ₂ may be selectedbased on the question that was selected for question 432 ₁ and/or theresponse to question 432 ₁ provided in interface element 433 ₁. In thismanner, follow-up questions customized to the ongoing assessment may beselected by Recruiter and/or suggested by the electronic recruitingsystem.

FIG. 4E depicts an example note-taking window displayed on a recruitingterminal. The note taking window 439 comprises an interface element 440in which notes can be written or drawn (in the case of a touch screen),typed, dragged-and-dropped (E.g. for pictures and/or video clips), etc.The interface element 441 may bring up a window for selecting an audioclip from memory to be added to the note and/or may bring up an audiorecording application (using a microphone of the recruiter terminal 128a) for capturing an audio component of the note. The interface element442 may bring up a window for selecting a video clip from memory to beadded to the note and/or may bring up a video recording application forcapturing (using a camera of the recruiter terminal 128 a) a videocomponent of the note. The interface element 443 may bring up a windowfor selecting an image from memory to be added to the note and/or maybring up a picture-taking application for capturing (using a camera ofthe recruiter terminal 128 a) a picture component of the note.

When a note is generated and subsequently saved to memory using thenote-taking window, the resulting note may be associated with one ormore candidates, organizations, recruiters, and/or events such that thenote may be accessible from various windows and/or in various ways fromthe recruiting terminal 128 a. Which candidate(s), organization(s),recruiter(s), and/or event(s) a note is associated with may be selectedby the user creating the note and/or may be automatically determinedbased on context information such as, for example, who is logged intothe recruiter terminal 128 a, the date and time, the window from whichthe note-taking window 439 was opened, etc.

FIG. 4F depicts an example interview scheduling window displayed on arecruiting terminal. In FIG. 4F there is a calendar interface element444 into which one or more of the interface elements 405 ₁-405 ₅ may bedragged to schedule interview(s) (or meeting(s) or other interactions)with the candidate(s). In response to dragging the interface element 405_(i) into the element 444, an invite may be sent to Candidate i. Anindication of the scheduled interview in window 444 may be displayed ina first manner (e.g., in a first color) before Candidate i accepts theinvite and in a second manner (e.g., in a second color) after Candidatei accepts the invite. Upon dragging the element 405 _(i) to a particularday on the calendar element 444, the system may check the calendar ofCandidate i (which may be stored, for example, on server(s) 114) andthen automatically schedule the interaction between Candidate i andRecruiter for a timeslot of that day that is available on both Candidatei and Recruiter's calendars. Where multiple ones of the elements 405₁-405 ₅ (corresponding to multiple candidates) are dragged to thecalendar element 444, the recruiting system may attempt to accommodatethe calendars of all selected candidates and Recruiter. Where all cannotbe accommodated, the system may prioritize placement of the candidateson the calendar based on, for example, candidate profile information(including a cultural fit score), a priority-level assigned to thecandidates by Recruiter (or another member of Organization), and/orpriority-levels assigned to Recruiter and/or Organization assigned bythe candidates. Priority-levels of candidate assigned by recruiters maybe hidden from candidates and priority-levels of organizations assignedby candidates may be hidden from recruiters.

For example, where a first recruiter of a first organization and asecond recruiter of a second organization each want to interact withcandidate i during the same timeslot on the same day, the system mayschedule candidate i to interact with: the recruiter assigned a higherpriority by candidate i, the organization assigned a higher priority bycandidate i, the organization for which candidate i is a better culturalfit, and/or based on some combination of these and/or other factors.

FIG. 4G depicts another example interview scheduling window displayed ona recruiting terminal. The window 446 in FIG. 4G may be used forautomated scheduling of interactions (e.g., interviews) between one ormore candidates and one or more recruiters and/or interviewers. Thewindow 446 comprises an interface element 447 for selecting a date ordates to be scheduled. The interface element 452 may display a previewof Recruiter's calendar for the selected date(s). The interface element448 may display the selected candidates to be scheduled on the selecteddate(s). Associated with each candidate is an interface element 449which Recruiter may use to prioritize his/her desire to interact withthe selected candidates. Selection of the interface element 450 maycause the recruiting system to process the information in element 448along with the information in the calendars of the selected candidatesto generate a proposed schedule that best accommodates Recruiter'sschedule and the selected candidates' schedules based onpriority-levels, cultural fit scores, and/or other factors. A preview ofa successful scheduling may then be displayed. Such a preview mayindicate candidates who could not be scheduled given the currentcriteria. If the Recruiter is happy with the proposed schedule s/he maythen select the interface element 451 to send invites to the selectedcandidates. If any of the invites are declined, the system may suggestalternate candidates to be scheduled for the timeslots vacated by thedeclined invitations.

The preceding paragraph described an example implementation in which thecandidates' and Recruiter's calendar are taken into account when settingRecruiter's calendar. In another implementation, the calendars of otherRecruiters may also be taken into account. For example, each recruiterof each organization and each candidate participating in a recruitingevent may submit their desired interactions along with a priority-levelof those interactions. Once all submissions are submitted (e.g., at apre-determined deadline set by the event), the recruiting system mayalgorithmically populate the calendars of all recruiters and candidatesin an attempt to maximize the number of candidates that get to interactwith their preferred organizations and/or to maximize the number ofpreferred candidates that recruiters get to interact with. Suchautomated scheduling may help minimize scheduling conflicts as comparedto the candidates and recruiters manually setting their calendars.

Any of the windows described with reference to FIGS. 4A-4G may, forexample, be populated by pulling the underlying information from thedatabase(s) 124 via an API.

FIGS. 5A-5C depict a flowchart illustrating an example process forat-event management of recruiting information. For ease and clarity ofdescription, the process is described with reference to a recruiter(“Recruiter”) using the example recruiting terminal 128 a. Referring toFIG. 5A, the example process begins with block 501 in which therecruiting app 130 a is launched on the terminal 128 a and Recruiterlogs in by, for example, typing his username and password. In block 502,a list of past, present, and/or future recruiting events is displayedsuch as, for example, shown in window 300 of FIG. 3A. In block 503,Recruiter selects one of the events in the list (e.g., by selecting aninterface element 305 _(i) in FIG. 3A) and, as a result, candidate info(e.g., profiles, résumés/CVs, etc.) and/or other resources (e.g.,executable forms, organizational promotional materials, etc.) aredownloaded from the server(s) 114 to the terminal 128 a. In block 504,Recruiter causes (e.g., by selecting interface element 316) the terminal128 a to display a searchable and/or sortable list of candidatesassociated with the selected event, such as is shown in window 400 ofFIG. 4A. In block 505, the terminal 128 a reads an identifier from acandidate terminal (e.g., optically reads a QR code or reads an ID usingNFC) and searches the list of candidates for a candidate associated withthe read identifier.

In block 506, it is determined whether a candidate associated with theread identifier has been found in the candidate list. If a candidateassociated with the read identifier is found, the process proceeds toblock 510. If no candidate associated with the read identifier is found,then in block 507 a window for adding a candidate (and associating thatcandidate with the read identifier) is displayed. In block 508, thecandidate's information is entered and the candidate is added to thecandidate list (and may be subsequently uploaded to the server(s) 114).

In block 510, a profile and/or résumé/CV of the selected candidate alongwith interface elements for viewing/inputting assessments of theselected candidate and/or for scheduling an interaction (e.g.,interview) with the selected candidate may be displayed and/or madeaccessible to Recruiter. If Recruiter selects an interface element (e.g.410) to view and/or input an assessment of the selected candidate, thenthe process advances to block 512, which is described below withreference to FIG. 5B. If Recruiter selects an interface element (e.g.,to schedule an interaction (e.g., an interview) with the selectedcandidate, then the process advances to block 514, which is describedbelow with reference to FIG. 5C.

Referring to FIG. 5B, in block 518, a window for selecting completed andongoing assessment forms and/or for selecting a blank assessment formfor inputting a new assessment of the selected candidate (e.g., window401 in FIG. 4B) is displayed. If Recruiter selects an interface elementcorresponding to a blank assessment form (e.g., element 421 ₁), then theprocess advances to block 520. In block 520, an assessment form, such asthe form described above with reference to FIG. 4D, is displayed, andRecruiter inputs his/her assessment of the selected candidate using theinterface elements of the form. In instances where the information isinput to the assessment form while the terminal 128 a does not have anetwork connection, the completed assessment form may be stored locallyon the terminal 128 a and uploaded to the server(s) 114 upon theterminal 128 a establishing a network connection. Where the terminal 128a does have a network connection while the assessment form is beingfilled out, the information input to the form may be uploaded to theserver(s) 114 and/or shared to other recruiting terminals 128 in, ornear, real-time (where the appropriate permissions are in place).

Returning to block 518, if Recruiter selects an interface element (e.g.,element 418 ₁) corresponding to an assessment form that was previouslycompleted or is currently being filled out on another recruitingterminal, then the process advances to block 527. In block 527, acompleted or in-progress assessment form, such as the form describedabove with reference to FIG. 4C, is displayed. An in-progress assessmentform may be viewable on the terminal 128 a where there is an existingnetwork connection(s) that connect the terminal 128 a to the terminal onwhich the assessment form is being filled out. Where the assessment formis in-progress and being filled out by another recruiter, Recruiter mayor may not have permission to input information into the form oroverride information input by the other recruiter.

Referring to FIG. 5C, in block 541 an interface element comprising theinterviewer's event calendar is displayed on the recruiting terminal.The interviewer may be Recruiter or may be another member ofOrganization. In block 542, an interface element corresponding to theselected candidate is dragged onto the calendar interface element to aday and/or event for which the interview is to be scheduled. In block543, the interviewer's calendar and the selected candidate's calendar(which may be stored on the recruiter terminal and/or on the server(s)114) may be checked to determine a timeslot that works for both.Timeslots meeting such criteria may be presented and the Recruiter mayselect one or more of them to suggest to the selected candidate. Inresponse to the selection of the timeslot(s) an invitation may be sentto the selected candidate. In block 544 the selected candidate mayaccept the invitation for one of the timeslots. In block 545 both theinterviewer's calendar and the selected candidate's calendar may beupdated to reflect the newly-scheduled interview.

FIG. 5D depicts a flowchart illustrating an example interview schedulingprocess. Whereas FIG. 5C illustrated a relatively simple process ofscheduling a single candidate and a single interviewer, FIG. 5Dillustrates a process for scheduling potentially-conflicting interviewsof multiple candidates by multiple interviewers. In block 550, each ofthe multiple interviewers brings up his/her calendar on a recruitingterminal and each of the multiple candidates brings up his/her calendaron a candidate terminal. In block 551, each candidate drags desiredorganizations and/or interviewers onto his/her calendar and assigns apriority-level to each. In block 552, each interviewer drags desiredcandidates onto his/her calendar and assigns a priority-level to each.In block 553, the recruiting system processes all of the submittedcalendars and their accompanying prioritizations to populate eachcandidate's calendar and each recruiter's calendar as optimally aspossible. That is, to try and maximize the number of candidates who geta timeslot with their highest-priority organizations and/or maximize thenumber of interviewers who get a timeslot with their highest-prioritycandidates. In block 554, each interviewer's schedule and eachcandidate's schedule is saved to his/her respective calendar and anotification that the scheduling is complete is sent to each.

FIG. 6 depicts components of an electronic recruiting management systemdeployed at a recruiting event. Shown is a floor plan of an event(“Event”) at which there are sensors 602 ₁-602 ₇, a check-in booth 601,organization booths 604 ₁-604 ₃, check-in terminals 606 ₁-606 ₄,candidate terminals 608 ₁-608 ₆, and recruiter terminals 610 ₁-610 ₆.

Each of candidate terminals 608 ₁-608 ₆ may be substantially similar toone of the candidate terminals 102 a and 102 b described above withreference to FIG. 1. Each of the recruiter terminals 610 ₁-610 ₆ may besubstantially similar to one of the recruiter terminals 128 a and 128 bdescribed above with reference to FIG. 1.

Each of the sensors 602 ₁-602 ₇ may comprise circuitry configured towirelessly detect the presence and/or location of recruiting terminals,candidate terminals, and/or other computing devices. Each of the sensors602 ₁-602 ₇ may, for example, passively listen to Wi-Fi and/or otherwireless network channels to detect computing devices communicating onthose channels. Upon detecting a computing device (e.g., a candidateterminal), the sensors 602 ₁-602 ₇ (where i is an integer between 1 and7) may log the presence of the device by storing a unique identifier(e.g., a MAC address and/or SIM card serial number) of the computingdevice to memory (e.g., uploading to memory 122). The sensors of thedetected computing device may additionally determine, and subsequentlylog in memory, the location of the detected computing device. Locationof devices at the event may be determined by, for example, triangulationbased on which of the sensors 602 ₁-602 ₇ detected which communicationsfrom the computing device at which time, and/or based on signalstrength(s) from the detected computing device incident on one or moreof the sensors 602 ₁-602 ₇. Other methods of indoor navigation may beused in addition to, or instead of, the location determination based onsensors 602.

Each of the check-in terminals 606 ₁-606 ₄ may comprise circuitryconfigured to log candidate and/or recruiter terminals as being presentin the immediate vicinity of the check-in terminal. For example, ascandidates and/or recruiters enter the event, they may stop by thecheck-in booth 601 and allow the check-in terminal 606 ₄ to scan theirrespective candidate and recruiter terminals. Upon such a scan, theterminal 606 ₄ may update an event roster which may be stored on theserver(s) 114 and may be accessible by other candidates, recruiters,and/or event administrators. As another example, as candidates stop byOrganization B's booth 604 ₁, they may present their respectivecandidate terminals for scanning by check-in terminal 606 ₁. Such scansmay be used, for example, to maintain a waiting list for candidatesseeking to talk with recruiters of Organization B, for communicatingcandidate information to Organization B, and/or for communicatingOrganization B information to the candidates. In an exampleimplementation, each of the check-in terminals 606 ₁-606 ₄ may be arecruiter terminal that has been configured into a check-in terminalmode in which only limited functions of the recruiter terminal areaccessible until an administrator of the terminal changes theconfiguration.

To illustrate, at the time instant shown in FIG. 6, information from thesensors 606 ₁-606 ₄ may be used to determine that two recruiterterminals (610 ₁ and 610 ₂) and three candidate terminals (608 ₂-608 ₄)are at the booth 604 ₁, that two recruiter terminals (610 ₃ and 610 ₄)and only one candidate terminal (608 ₅) are at booth 604 ₂, and that tworecruiter terminals (610 ₅ and 610 ₆) and only one candidate terminal(608 ₆) are at booth 604 ₃. Additionally, historical information fromthe sensors 606 ₁-606 ₄ may be used to determine where the recruiterterminals and/or candidate terminals were previously (e.g., which boothscandidates previously visited). Information from the sensors may be usedby event administrators to, for example, distribute (e.g., throughnotification messages to candidate terminals) attendees with a goal ofreducing booth wait times and increasing interactions overall.Information from the sensors 606 ₁-606 ₄ may be used by event recruitersto, for example, determine which candidates to target, manage recruiterscheduling, determine when to send out notifications for candidate tovisit their booths, determine where to locate their booths and/orrecruiters, etc. Information from the sensors 606 ₁-606 ₄ may be used bycandidates to, for example, determine which booths to visit and when,which candidates to network with, etc.

FIG. 7A depicts a flowchart illustrating at-event candidate andrecruiter matchmaking using an electronic recruiting management system.In block 720, Candidate is at a recruiting event (“Event”) with his/hercandidate terminal 608 _(X) and a recruiter (“Recruiter”) ofOrganization is at Event with his/her recruiter terminal 610 _(X). Inblock 721, the positions of terminal 608 _(X) and terminal 610 _(X) aretracked (e.g., via sensors 602 ₁-602 ₇). In block 722, it is determinedthat terminal 608 _(X) is within a determined proximity (e.g., 50 feet)of terminal 610 _(X). This may occur, for example, when Candidate iswalking by Organization's booth. In block 723 it is determined that acompatibility between Candidate and Organization (e.g., based on workcultural and/or personality assessments) is above a threshold.

In block 724, Recruiter is alerted (e.g., via a push notification tohis/her recruiter terminal) as to the proximity of Candidate. The alertmay include some information about Candidate such as Candidate's collegemajor and/or the compatibility score between Candidate and Organization.In block 725, Candidate is alerted (e.g., via a push notification tohis/her candidate terminal) as to the proximity of Recruiter. The alertmay include some information about Recruiter and/or Organization such asnumber and/or types of positions that Organization is looking to filland/or the compatibility score between Candidate and Organization. Inblock 726, either or both Candidate and Recruiter may respond to thenotification (e.g., Recruiter may push a “send invite” interface elementincluded in the notification and/or Candidate may push a “get on waitinglist” interface element included in the notification) to trigger furthersteps toward an interaction between Candidate and Recruiter.

FIG. 7B depicts a flowchart illustrating at-event interview schedulingand coordination using an electronic recruiting management system. Theprocess begins with block 728 in which a plurality of candidates are atthe Event depicted in FIG. 6 and carrying their respective candidateterminals. In block 730, as the candidates walk around the event, eachcandidate's position may be tracked by the sensors 602 ₁-602 ₇ and maybe logged on the server(s) 114. Additionally, as the candidates check inat various booths 601 and/or 604 and/or interact with recruiters, thoseevents may also be logged on the server(s) 114. In block 732, aparticular candidate (“Candidate”), using his/her candidate terminal,pulls up a list of organizations that are at the event and, in block733, selects an organization with which s/he would like to meet. Inblock 734, the candidate terminal displays the current approximate waittime for that organization's booth, a suggested time for Candidate tovisit the booth, and/or any other information which may be calculatedbased on the candidate positioning, check-in, and/or interactioninformation. In another implementation, the list of organizations pulledup in block 732 may be sortable and/or filterable based on, for example,current wait times, whether or not Candidate has already visited theorganization's booth, how many candidate have visited the organization'sbooth, booths that have the most visits by candidates similar in someway to Candidate, and/or any other filtering/sorting parameter which canharness the candidate position tracking information, check-ininformation, and/or the candidate and organization profile informationavailable in the electronic recruiting system.

FIG. 7C depicts a flowchart illustrating networking features of anelectronic recruiting management system. The process of FIG. 7C beginswith block 740 in which Candidate A and Candidate B are both at an eventcarrying their respective candidate terminals. In block 741, the twocandidates visit various organization booths and interact with variousrecruiters over the course of the event. In block 742, an analysis ofthe two candidates' movements and logged interactions over the course ofthe event indicates that they visited many of the same booths but didnot interact with each other. In response, in block 743, each of the twocandidates receives a notification (e.g., email or message to his/hercandidate profile) with a recommendation to subscribe to the otherand/or meet the other (e.g., at a mixer put on as part of the event orat a future event).

FIG. 8A depicts an example public candidate profile window provided byan electronic recruiting management system. Shown is a candidate profilewindow of candidate John Doe. The profile picture interface element 801comprises a picture that John Doe selected for others to see whenviewing his profile. The interface element 802 may comprise the namethat John Doe has chosen for others to see when viewing his profile. Theinterface element 803 comprises a brief description or headline thatJohn Doe has typed in for others to see when viewing his profile. Theinterface element 804 comprises contact information that John Doe haschosen for others to be able to see when viewing his profile.

Interacting with the interface element 805 may bring up a messagingwindow for sending a message to John Doe. When a user interacts with theinterface element 806, the user's profile may be subscribed to JohnDoe's profile. When a user interacts with the interface element 807, theuser may recommend John Doe (e.g., in general and/or for a specificposition) and the recommendation may post to John Doe's profile, theuser's profile, and/or may be sent to the organization (e.g., theorganizations profile in the electronic recruiting system and/or to theorganization's résumé/CV collection email address) to which John Doe isbeing recommended.

The interface element 810 may comprise a plurality of interface elements808 each of which corresponds to an organization, candidate, and/orevent to which John Doe is subscribed. Clicking on an interface element808 _(i) may open a profile window of the corresponding candidate,organization, or event. Interacting with the interface element 809 maybring up a window displaying all candidates, organizations, and/orevents to which John Doe is subscribed. In addition to, or instead of,corresponding to profiles to which John Doe is subscribed, one or moreinterface elements 808 may correspond to an organization of which JohnDoe is a member or employee.

The interface element 817 may comprise information about John Doe'sacademic credentials and may comprise a plurality of interface elements815 and 816. Each interface element 815 _(i) may correspond to a schoolJohn Doe attended and the corresponding interface element 816 _(i) maycomprise details about John Doe's involvement with the school.

The interface element 820 may comprise documents such as John Doe'srésumé(s)/CV(s), publications, projects, etc. Interacting with one ofthe interface elements 818 may bring up a copy (e.g., a .pdf or .htmlfile) of the document associated with the interface element 818. Eachinterface element 819 may comprise a snapshot, a summary, excerpt, etc.,from the corresponding document.

The interface element 821 may comprise a list of skills,characteristics, etc., that pertain to John Doe. The list may bepopulated from a standardized or uniform set of tags.

When the interface element 812 is selected (as indicated by the heavyline in FIG. 8A), the interface element 814 is displayed in thecandidate profile window. The interface element 814 may comprise, forexample, work history details, academic history details, affiliations,association memberships, John Doe's interests, John Doe's publications,John Doe's projects, etc. The information interface element 814 may havebeen manually entered by John Doe, read from documents uploaded by JohnDoe, and/or imported from other websites or databases.

Now referring to FIG. 8B, when the interface element 813 is selected (asindicated by the heavy line), one or more interface elements 831 may bedisplayed in the candidate profile window. Each interface element 831_(i) may comprise a message or status update posted by John Doe and mayindicate the day/time at which it was posted. When a message refers toan organization, candidate, or event that has a profile in theelectronic recruiting system, the organization, candidate, or event namemay appear as an interface element 832 that links to an associatedprofile.

Now referring to FIG. 8C, when the interface element 822 is selected (asindicated by the heavy line), interface elements 890, 891, 892, and 893may be displayed in the candidate profile. Each interface element 890(for simplicity of illustration, only one is shown) may comprise adescription (subject matter, dates, sponsors, thesis, conclusions, etc.)of a project With which the candidate has been involved. Each interfaceelement 891 may have a corresponding interface element 892 whichcomprises tags (e.g., the industry to which the project is applicable,the technology used for the project, etc.) that provide quick, easilysearchable information about the project. Each interface element 893 maybe, or link to, a file (e.g., images, white papers, presentations,samples of code, data sets, etc.) attached to the project.

Each interface element 891 may have a corresponding one or moreinterface elements 892 (two are shown for illustration), each of whichcorresponds to another person who worked on the project. In instanceswhen the person associated with element 892 _(i) has a profile on in theelectronic recruiting system, the interface element 892 _(i) may link tothat person's profile. In instances when the person does not have aprofile in the electronic recruiting system, an invite to create aprofile in the recruiting system may be sent to that person in responseto the candidate listing him/her as a collaborator on the project. Theinvite may, for example, give the person the option of creating aprofile with pre-populated information pertaining to the project. Whenone collaborator on a project updates information pertaining to thatproject, the updates may be automatically updated on the othercollaborators' profiles and/or the other collaborators may be send anotification the update has been made and given the option to add theupdates to their respective profiles.

FIG. 8D depicts an example private candidate home window provided by anelectronic recruiting management system. FIG. 8D displays an examplewindow via which a candidate (in this case John Doe) may maintainhis/her profile (e.g., as shown in FIGS. 8A and 8B) and also interactwith the electronic recruiting system to perform variousrecruiting-related processes described herein. The interface elements840, 841, and 842 may be used for navigating between the window shown inFIG. 8D, the window shown in FIG. 8E, and a messaging window.

Still referring to FIG. 8D, the profile picture displayed in the profilewindow of FIGS. 8A and 8B may be changed via interaction with interfaceelement 846. The name displayed in the profile window of FIGS. 8A and 8Bmay be changed via interaction with interface element 843. Theheadline/brief description displayed in the profile window of FIGS. 8Aand 8B may be changed via interaction with the interface element 844.The contact information displayed in the profile window of FIGS. 8A and8B may be changed via interaction with interface element 845.Interaction with the interface elements 846 and subsequent clicking ortapping of the interface element 847, an interface element 831containing the message may be posted to the profile window shown in FIG.8B.

The interface element 853 may comprise a list of organizations to whichJohn Doe is subscribed in the electronic recruiting system and/or ofwhich John Doe is a member (whether it be as employee, volunteer, etc.).Each element 852 _(i) may correspond to one such organization and may,in turn, comprise an element 857 _(i) that links to the organization'sprofile in the recruiting system, an element 858 _(i) that shows acompatibility score between John Doe and the organization, and anelement 859 _(i) that links to the profile of particular recruiter atorganization with whom John Doe has interacted. The list may be filteredand/or sorted based on any number and/or variety of criteria using theinterface element 851.

The interface element 855 comprises a list of events that John Doe issubscribed to in the recruiting system and/or has attended or isplanning to attend. Each event in the list may correspond to an element854 which may link to the event's profile and/or an event organizer'sprofile. The interface element 856 may comprise statistics regardingJohn Doe's profile such as number of profile views, time since lastprofile view, number of organizations, candidates, and/or eventssubscribed-to, number of organizations, candidates, and/or events thatare subscribed to John Doe's profile, etc.

The interface element 848 may comprise a feed of messages fromorganizations, candidates, and/or events to which John Doe issubscribed. Each interface element 850 _(i) may comprise a message orstatus update posted by an organization, candidate, or event and mayindicate the day/time at which it was posted. When a message refers toan organization, candidate, or event that has a profile in theelectronic recruiting system, the organization, candidate, or event namemay appear as an interface element 849 that links to an associatedprofile.

Now referring to FIG. 8E, the interface element 881 may provide a searchtool for searching to discover organization profiles that meet selectedcriteria (e.g., a threshold compatibility score). Search/filter criteriamay be entered via the interface element 882 and the results may bedisplayed in the interface element 883. The interface element 884 mayprovide a search tool for searching to discover candidate and/orrecruiter profiles that meet selected criteria (e.g., a thresholdcompatibility score). Search/filter criteria may be entered via theinterface element 885 and the results may be displayed in the interfaceelement 886. The interface element 887 may provide a search tool forsearching to discover event profiles meeting selected criteria (e.g., athreshold compatibility score). Search/filter criteria may be enteredvia the interface element 882 and the results may be displayed in theinterface element 889.

The interface element 860 may comprise a list of organizations to whichit is suggested that John Doe subscribe. The suggestions may begenerated based on, for example, analysis by the recruiting system of:John Doe's profile, profiles to which John Doe is subscribed, theorganizations' profiles, profiles to which the organizations aresubscribed, scores indicating compatibility between John Doe and theorganizations, John Doe's past interactions, John Doe's scheduledinteractions, and/or information in John Doe's documents. Each interfaceelement 867 _(i) may correspond to one of the suggested organizationsand may, in turn, comprise: an interface element 862 _(i) that links tothe organization's profile, an interface element 864 _(i) that shows afit score (e.g., based on a workplace culture questionnaire) betweenJohn Doe and the organization, and an interface element 866 _(i) thatgives a brief description of the organization.

The interface element 871 may comprise a list of people (e.g.,candidates and/or recruiters) to which it is suggested that John Doesubscribe. The suggestions may be generated based on, for example, ananalysis by the recruiting system of: John Doe's profile, profiles towhich John Doe is subscribed, the peoples' profiles, profiles to whichthe people are subscribed, scores indicating compatibility between JohnDoe and the people, John Doe's past interactions, John Doe's scheduledinteractions, the peoples' past interactions, the peoples' scheduledinteractions, and/or information in John Doe's documents. Each interfaceelement 870 _(i) may correspond to one of the suggested persons and may,in turn, comprise: an interface element 868 _(i) that links to theperson's profile, and an interface element 869 _(i) that gives a briefdescription of the person.

The interface element 872 may comprise a list of events (e.g., jobfairs, diversity fairs, association fairs, expositions, etc.) that aresuggested for John Doe to attend and/or subscribe. The suggestions maybe generated based on, for example, an analysis by the recruiting systemof: John Doe's profile, profiles to which John Doe is subscribed, theevents' profiles, profiles to which the events' profiles are subscribed,organizations attending the events, people attending the events, scoresindicating compatibility between John Doe and the events, John Doe'spast interactions, John Doe's scheduled interactions, and/or informationin John Doe's documents. Each interface element 875 _(i) may correspondto one of the suggested events and may, in turn, comprise: an interfaceelement 873 _(i) that links to the event's profile, and an interfaceelement 874 _(i) that gives a brief description of the event.

The interface element 876 may comprise a list of requisitions (e.g., jobopenings, elected positions, etc.) to which it is suggested that JohnDoe apply. The requisitions may be stored in the server(s) 114 which mayfunctions as the organizations' applicant tracking systems and/or whichmay import the requisitions from organizations' applicant trackingsystems and/or other sources on the Internet. The suggestions may begenerated based on, for example, an analysis by the recruiting systemof: John Doe's profile, the events' profiles, subscriptions associatedwith the events' profiles, organizations attending the events, peopleattending the events, scores indicating compatibility between John Doeand the events, John Doe's past interactions, John Doe's scheduledinteractions, and/or information in John Doe's documents. Each interfaceelement 879 _(i) may correspond to one of the suggested requisitions andmay, in turn, comprise: an interface element 877 _(i) that gives a briefdescription of the requisition and/or links to the requisition (e.g., onthe associated organizations profile), and an interface element 878 _(i)via which John Doe can submit an application for the requisition. Forexample, upon clicking or tapping the interface element 878 _(i) JohnDoe's résumé/CV and/or other information from John Doe's profile in theelectronic recruiting system may be electronically submitted to theorganization associated with the requisition. The interface element 880may enable John Doe to apply for multiple requisitions, possiblyassociated with multiple organizations, in a single interaction (e.g.,click or tap). For example, an organization may associate requisitefields of information with a particular requisition and, in response toa candidate clicking to apply to that requisition, those fields ofinformation may be pulled from the candidate's profile, formatted asconfigured by the organization, and submitted to the organizationsapplicant tracking system.

Any of the windows described with reference to FIGS. 8A-8E may, forexample, be populated by pulling the underlying information from thedatabase(s) 124 via an API and/or other interface. Any of the windowsdescribed with reference to FIGS. 8A-8E may, for example, be viewed on acandidate terminal 102, a recruiter terminal 128, or any other suitablecomputing device.

FIG. 9A depicts an example public event profile window provided by anelectronic recruiting management system. Shown is an event profilewindow of Event A. The profile picture interface element 902 comprises apicture that an administrator of the event profile selected for othersto see when viewing Event A's profile. The interface element 802 maycomprise the name that Event A has chosen for others to see when viewingthe profile. The interface element 904 comprises a brief description orheadline that the administrator of Event A's profile has typed in forothers to see when viewing the profile.

When a user interacts with the interface element 905, the user's profilemay be subscribed to Event A's profile. When a user interacts with theinterface element 907, Event A may be added to the user's calendarand/or a reminder for Event A may be set in a list of reminders in theuser's profile. Interacting with the interface element 909 may bring upa messaging window for recommending Event A to one or more other personsand/or organizations. Interacting with the interface element 910 maybring up a window via which the user can sponsor Event A (e.g., make adonation, display that user is a sponsor of Event A on Event A's profileand/or on another website, and/or advertise Event A on the user'sprofile and/or on another website).

The interface element 917 may comprise information about Event A suchas, for example, a date of Event A, location of Event A, informationabout organizations registered to attend, information about candidatesregistered to attend, information about requisitions that will beinterviewed, industries in which Event A attendees are involved, andinformation about past occurrences of Event A. The information in theinterface element 917 may be populated from a standard set of tags, forexample. The interface element 918 may comprise a list of events similar(e.g., in any of the information in element 917, in candidates and/ororganizations that are subscribed, etc.) to Event A. Each interfaceelement 920 _(i) may correspond to a similar event and may, in turn,comprise an interface element 919 _(i) that links to the similar event'sprofile and an interface element 920 _(i) that, when interacted with,subscribes the user to the similar event. The interface element 922 maycomprise a list of other persons, organizations, and/or events whoseprofiles are subscribed to Event A; each interface element 923 _(i) maycorrespond to one such candidate and each interface element 924 _(i) maycorrespond to one such organization.

The interface element 915 may comprise a long-form description of EventA. The interface element 916 may comprise a map of Event A. The map maybe a street map and/or an indoor map of Event A. The interface element913 may comprise a list of people (e.g., administrators, coordinators,etc.) of Event A. For each person in interface element 913 there may bean interface element 911 _(i) that links to his/her profile in theelectronic recruiting system and/or an interface element 912 _(i) thatprovides a headline or brief bio of the person. The interface element914 may comprise statistics regarding Event A's profile such as numberof profile views, time since last profile view, number of organizations,candidates, and/or events subscribed-to, number of organizations,candidates, and/or events that are subscribed to John Doe's profile,etc.

When the interface element 906 is selected (as indicated by the heavyline in FIG. 9A) the window of FIG. 9A is displayed. When the interfaceelement 908 is selected (as indicated by the heavy line in FIG. 9B), thewindow of FIG. 9B is displayed.

Now referring to FIG. 9B, the interface element 925 may comprise a feedof messages from organizations, candidates, and/or events to which JohnDoe is subscribed. Each interface element 928 _(i) may comprise amessage or status update posted by an organization, candidate, or eventand may indicate the day/time at which it was posted. When a messagerefers to an organization, candidate, or event that has a profile in theelectronic recruiting system, the organization, candidate, or event namemay appear as an interface element 926 that links to an associatedprofile.

Information elements of the event profile may be accessible (e.g., viaan API) such that they may be reflected on an organization's profile inthe electronic recruiting system and/or on an organization's website(e.g., on Organization A's recruiting homepage atwww.organizationA.com/recruiting).

FIG. 9C depicts an example event private profile administration windowprovided by an electronic recruiting management system. FIG. 9C displaysan example window via which an event organizer/administrator (in thiscase the administrator of Event A's profile) may maintain Event A'sprofile (e.g., as shown in FIGS. 9A and 9B) and also interact with theelectronic recruiting system to perform various recruiting-relatedprocesses described herein. The profile picture displayed in the profilewindow of FIGS. 9A and 9B may be changed via interaction with interfaceelement 940. The name displayed in the profile window of FIGS. 9A and 9Bmay be changed via interaction with interface element 941. Theheadline/brief description displayed in the profile window of FIGS. 9Aand 9B may be changed via interaction with the interface element 942.The people and corresponding descriptions shown in the interface element913 of FIG. 9A may be changed via interaction with interface elements943 and 944.

The interface element 945 may comprise a list of organizations that aresuggested for the administrator of Event A to invite to attend Event A.The suggestions may be generated based on, for example, analysis by therecruiting system of: Event A's profile, the organizations' profiles,subscriptions associated with the organizations' profiles, pastattendance of Event A, candidates registered to attend Event A, and/ororganizations registered to attend Event A. Each interface element 959_(i) may correspond to one of the suggested organizations and may, inturn, comprise: an interface element 946 _(i) that links to theorganization's profile, an interface element 947 _(i) that gives a briefdescription of the organization.

The interface element 948 may comprise a list of people (e.g.,candidates and/or recruiters) that are suggested to be invited to EventA. The suggestions may be generated based on, for example, an analysisby the recruiting system of: Event A's profile, the peoples' profiles,subscriptions associated with the people's profiles, scores indicatingcompatibility between Event A and the people, past attendance of EventA, candidates registered to attend Event A, and/or organizationsregistered to attend Event A. Each interface element 870 _(i) maycorrespond to one of the suggested persons and may, in turn, comprise:an interface element 868 _(i) that links to the person's profile, and aninterface element 869 _(i) that gives a brief description of the person.

The interface element 951 may provide a search tool for searching todiscover organization profiles meeting selected criteria (e.g., in aparticular location and/or industry). Search/filter criteria may beentered via the interface element 952 and the results may be displayedin the interface element 953. The interface element 954 may enablesending invitations to Event A to all (or a selected subset)organizations meeting in the interface element 953. The interfaceelement 955 may provide a search tool for searching to discovercandidate and/or recruiter profiles meeting selected criteria (e.g., ina particular location and/or industry). Search/filter criteria may beentered via the interface element 956 and the results may be displayedin the interface element 957. The interface element 958 may enablesending invitations to Event A to all (or a selected subset)organizations in the interface element 957.

Any of the windows described with reference to FIGS. 9A-9C may, forexample, be populated by pulling the underlying information from thedatabase(s) 124 via an API and/or other interface. Any of the windowsdescribed with reference to FIGS. 8A-8E may, for example, be viewed on acandidate terminal 102, a recruiter terminal 128, or any other suitablecomputing device.

FIG. 10A depicts an example public organization profile window providedby an electronic recruiting management system. Shown is an organizationprofile window of Organization A. The profile picture interface element1001 comprises a picture that an administrator of Organization A'sprofile selected for others to see when viewing Organization A'sprofile. The interface element 1002 may comprise the name that Event Ahas chosen for others to see when viewing the profile. The interfaceelement 1003 comprises a brief description or headline that theadministrator of Event A's profile has typed in for others to see whenviewing the profile.

The interface element 1004 may display a compatibility score (e.g.,based on work culture questionnaires) between Organization A and theuser viewing Organization A's profile. When a user interacts with theinterface element 1005, the user's profile may be subscribed toOrganization A's profile. Interacting with the interface element 1006may bring up a messaging window for recommending Organization A to oneor more other persons and/or events. Interacting with the interfaceelement 1008 may bring up a window via which the user can sponsorOrganization A (e.g., make a donation, display that user is a sponsor ofOrganization A on Organization A's profile, and/or on another website,and/or advertise Organization A on the user's profile and/or on anotherwebsite).

The interface element 1018 may comprise information about Organization Asuch as, for example, a website URL, and organization demographics suchas, for example, size, industry, college majors of members/employees,and/or diversity information. The information in the interface element1018 may be populated from a standard set of tags, for example. Theinterface element 1026 may comprise a list of organizations similar(e.g., in any of the information in element 1018, in what candidatesand/or organizations are subscribed to the organization, in whatcandidates and/or organizations the organization is subscribed to, etc.)to Organization A. Each interface element 1022 _(i) may correspond to asimilar organization and may, in turn, comprise an interface element1019 _(i) that links to the similar organization's profile, an interfaceelement 1020 _(i) that shows a compatibility score between John Doe andthe organization, and an interface element 1021 _(i) that, wheninteracted with, subscribes the user to the similar organization. Theinterface element 1023 comprises a list of other persons, organizations,and/or events whose profiles are subscribed to Organization A; eachinterface element 1024 _(i) may correspond to one such candidate andeach interface element 1025 _(i) may correspond to one suchorganization.

The interface element 1016 may comprise a long-form description ofOrganization A. The interface element 1017 may comprise a map ofOrganization A's location(s). The interface element 1011 may compriselist of people (e.g., administrators, Recruiters, etc.) of OrganizationA. For each person in interface element 1011, there is an interfaceelement 1009 that links to his/her profile in the electronic recruitingsystem and/or an interface element 1010 that provides a headline orbrief bio of the person. The interface element 1012 may comprise list ofother organizations (e.g., non-profits) of which Organization A is amember. The interface element 1015 may comprise statistics regardingOrganization A's profile such as number of profile views, time sincelast profile view, number of organizations, candidates, and/or eventssubscribed-to, number of organizations, candidates, and/or events thatare subscribed to Organization A's profile, etc.

When the interface element 1006 is selected (as indicated by the heavyline in FIG. 10A) the window of FIG. 10A is displayed. When theinterface element 1007 is selected (as indicated by the heavy line inFIG. 10B), the window of FIG. 9B is displayed.

Now referring to FIG. 10B, the interface element 1026 may comprise afeed of messages from organizations, candidates, and/or events to whichOrganization A is subscribed. Each interface element 1027 _(i) maycomprise a message or status update posted by an organization,candidate, or event and may indicate the day/time at which it wasposted. When a message refers to an organization, candidate, or eventthat has a profile in the electronic recruiting system, theorganization, candidate, or event name may appear as an interfaceelement 1028 that links to an associated profile.

FIG. 10C depicts an example recruiting dashboard window provided by anelectronic recruiting management system. The recruiting dashboard windowmay provide an interface for managing the content, layout, etc., of theprofile windows of FIGS. 10A and 10B and for managing recruitingprocesses. The recruiting dashboard window of FIG. 10C may typically beused by an organization's human resources and/or recruiting coordinator,for example. Interacting with the interface element 1030 may bring up awindow for editing the profile displayed in FIGS. 10A and 10B. Such awindow may be similar to the windows shown in FIGS. 8D and 9C. That is,such a window may comprise various interface elements for editingcorresponding interface elements of the profile windows in FIGS. 10A and10B.

Interacting with the interface element 1031 may bring up a window forassessing recruiter performance according to various metrics. An exampleof such a window is shown in FIG. 10D. Interacting with the interfaceelement 1032 may bring up a window for assessing various metricsassociated with the organization's attendance and/or activity at one ormore recruiting events. An example of such a window is shown in FIG.10E. Interacting with the interface element 1033 may bring up a windowfor managing an organization recruiting calendar. An example of such awindow is shown in FIG. 10F. Interacting with the interface element 1034may bring up a window for managing an organization's position/jobrequisitions. An example of such a window is shown in FIG. 10G.Interacting with the interface element 1035 may bring up a window forperforming a search to discover candidates and/or events that might besuitable for organization. An example of such a window is shown in FIG.10I.

FIG. 10D depicts an example recruiter assessment window provided by anelectronic recruiting management system. Interaction with the interfaceelement 1036 may enable selecting, filtering, and/or sorting theorganization's recruiters to generate the list of recruiters beingassessed in interface element 1037. The interface element 1038 may thendisplay statistics and/or recruiting performance metrics for therecruiters listed in interface element 1037.

The sorting/filtering of the list via interface element 1036 may bebased on any one or more of the metrics or statistics shown in interfaceelement 1038. For a particular recruiter (“Recruiter”) of a particularorganization (“Organization”), such metrics and/or statistics mayinclude, for example: number of events attended by Recruiter, list ofparticular events attended by Recruiter, number of candidates screenedby Recruiter, list of particular candidates screened by Recruiter,number of offers presented to candidates identified by Recruiter, numberof candidates identified by Recruiter that are ongoing in the interviewprocess, number of offers accepted/rejected by candidates identified byRecruiter, number of candidates identified by Recruiter that wereultimately awarded a position with Organization, subsequent performanceof such hires (e.g., based on internal performance reviews), statisticsregarding Recruiter's profile in the electronic recruiting system,and/or assessment scores that Recruiter has given to candidatesgenerally and/or to particular candidates. The interface element 1038may present the information in the form of, for example, lists, graphs,charts, etc. The information presented in interface element 1038 mayalso be presented such that recruiter(s) can, for example, be comparedside-by-side with other recruiters and/or year-over-year performance.

FIG. 10E depicts an example event assessment window provided by anelectronic recruiting management system. Interaction with the interfaceelement 1039 may enable selecting, filtering, and/or sorting the eventsto generate the list of events being assessed in interface element 1040.The interface element 1041 may then display statistics and/or recruitingperformance metrics for the events listed in interface element 1040.

The sorting/filtering of the list via interface element 1039 may bebased on any one or more of the metrics or statistics shown in interfaceelement 1041. For a recruiting coordinator of a particular organization(“Organization”) viewing the interface element 1041, such metrics and/orstatistics may include, for example: Organization's costs inparticipating in the event(s), number of candidates (perhaps meetingparticular, selected criteria) that attended the event(s), numbercandidates screened by Organization's recruiters at the event(s), numberof Organization positions filled by candidates identified at theevent(s), subsequent performance (e.g., based on internal performancereviews) of such candidates, list of candidates identified (e.g.,screened and recommended for interviewing) at the event(s), averagesassessment scores given by Organization's recruiters to candidatescreened at the event(s), average compatibility scores of candidates whoattended the event(s), number of referrals originated at the event(s),statistics regarding the number and/or rates at which candidateterminals were scanned by recruiter terminals and/or check-in terminalsat the event(s). The interface element 1041 may present the informationin the form of, for example, lists, graphs, charts, etc. The informationpresented in interface element 1041 may also be presented such thatevents can be compared side-by-side and/or year-over-year.

FIG. 10F depicts an example event scheduler window provided by anelectronic recruiting management system. Interface elements 1058, 1059,and 1060 may be displayed on a calendar and/or in a chronological list.Each element 1058 may correspond to a past event. Each element 1059 maycorrespond to an in-progress event. Each element 1060 may correspond toa future event.

Each interface element 1058 _(i) may provide the name of the associatedevent and may, when interacted with, bring up the associated event'sprofile in the electronic recruiting system. Each interface element 1051_(i) may indicate a status of the corresponding event. Each interfaceelement 1052 _(i) may, when interacted with, bring up a list ofcandidates who attended and/or are registered to attend the associatedevent and may indicate a status of each candidate (e.g., whether thecandidate was screened at a past event, individual and/or compositeassessment scores the candidate received at the past event, whether thecandidate is scheduled for further interviewing, whether the candidatesare high priority to be screened at a future event, a time at which thecandidate is to be screened at a future event, etc.). Each interfaceelement 1053 _(i), when interacted with, may bring up a window in whichassessments (e.g., submitted by recruiters via interface element 304 ofwindow 300 in FIG. 3A) of the associated event may be reviewed andanalyzed. Each interface element 1054 _(i), when interacted with, maybring up a window (e.g., with a calendar element) that displays theschedules of recruiters and/or interviewers attending an in-progressevent. Each interface element 1056 _(i), when interacted with, may bringup a window (e.g., with a calendar element and list of recruiters andinterviewers) via which the recruiting coordinator can schedulerecruiters and/or interviewers for the upcoming event. Each interfaceelement 1057 i may, when interacted with, bring up a window for creatingand/or uploading forms (e.g., assessment forms described with referenceto FIGS. 4B-4D.) and/or other resources such as, for example, theresources described with reference to FIGS. 2A and 2B.

Each interface element 1055 _(i) may bring up a window via which therecruiting coordinator or human resources manager can view (e.g., inreal-time and/or in periodic updates) recently-completed and in-progressassessment forms being filled out by recruiters and/or interviewersattending the in-progress event. In this manner, a recruiting manager orrecruiting coordinator can, at or near real-time, track the progressand/or value of particular recruiting events and/or recruiters inreal-time, can allocate and de-allocate resources to a particular eventdepending on current need, manage recruiter and/or interviewer schedules(e.g., to accommodate high-priority candidates), identify theparticularly strong candidates as soon as possible, etc.

FIG. 10G depicts an example requisition management window provided by anelectronic recruiting management system. The interface element 1061 mayenable selection of criteria for filtering and/or sorting a list ofrequisitions shown in the interface element. The requisitions may besorted by, for example, any of the information shown in interfaceelement 1064. Such information may include, for example, requirementsand/or qualifications for the position, salary to be paid for theposition, geographic location of the position, etc. The interfaceelement 1065 may comprise information about the pool of candidates fromwhich the requisition may be filled. Information about the pool ofcandidates may include, for example, number of candidates in theelectronic recruiting system that meet the qualifications/requirementsof the requisition, number of candidates already screened and/orinterviewed for the requisition, number of candidates scheduled to beinterviewed for the requisition, where the candidates in the pool whereidentified (e.g., via their online profiles, via paper résumé/CV, via aparticular event, via an external website or recruiting server, etc.),recruiter(s) associated with particular candidates in the pool, links toprofiles of candidates in the pool, assessment scores of candidates inthe pool, feedback regarding the organization received from candidatesin the pool, etc.

FIG. 10H depicts an example requisition creation window provided by anelectronic recruiting management system. Interaction with the interfaceelement 1066 may provide for entering information, (e.g., title,location, salary, etc.) about the requisition to be created. Interactionwith each of the interface elements 1068 _(i) may provide for enteringqualifications/requirements of the requisition being created. Theinterface element 1067 may display a size of the candidate pool for therequisition being created. The interface element 1067 may be updated inreal-time as the requirements for the position are input via theinterface elements 1068 and as new candidates are input to theelectronic recruiting system. The candidate pool size information ininterface element 1067 may be used in determining the qualifications forthe position as described, for example, with reference to FIGS. 11A and11B.

FIG. 10I depicts an example candidate and event discovery windowprovided by an electronic recruiting management system. For ease andclarity of description, it is assumed a recruiting coordinator ofOrganization is viewing the window of FIG. 10I. The interface element1073 may comprise a list of events that are suggested for theOrganization to attend. The suggestions may be generated based on, forexample, analysis by the recruiting system of: Organization's profile,the events' profiles, subscriptions associated with the events'profiles, past events attended by Organization, candidates registered toattend the events, candidate pool size requirements of Organizationsrequisitions, and/or other organizations registered to attend theevents. Each interface element 1076 may correspond to one of thesuggested events and may, in turn, comprise: an interface element 1074_(i) that links to the event's profile, an interface element 1075 _(i)that gives a brief description of the organization.

The interface element 1079 may comprise a list of people (e.g.,candidates and/or recruiters) that are suggested to join Organization.The suggestions may be generated based on, for example, an analysis bythe recruiting system of: Organization's profile, the peoples' profiles,profiles to which the people are subscribed, scores indicatingcompatibility between Organization and the people, and/or the people'srésumé/CV information. Each interface element 1080 _(i) may correspondto one of the suggested persons and may, in turn, comprise: an interfaceelement 1077 _(i) that links to the person's profile, and an interfaceelement 1078 _(i) that gives a brief description of the Event.

The interface element 1079 may provide a search tool for searching todiscover event profiles meeting selected criteria (e.g., in a particularlocation and/or industry). Search/filter criteria may be entered via theinterface element 1080 and the results may be displayed in the interfaceelement 1081. The interface element 1082 may enable subscribing toand/or registering for all (or a selected subset) of the events listedin the interface element 1081. The interface element 1083 may provide asearch tool for searching to discover candidate and/or recruiterprofiles meeting selected criteria (e.g., in a particular locationand/or industry). Search/filter criteria may be entered via theinterface element 1084 and the results may be displayed in the interfaceelement 1085. The interface element 1086 may enable subscribing to theprofile(s) of all (or a selected subset) of the people listed in theinterface element 1085.

Any of the windows described with reference to FIGS. 10A-10I may, forexample, be populated by pulling the underlying information from thedatabase(s) 124 via an API and/or other interface. Any of the windowsdescribed with reference to FIGS. 8A-8E may, for example, be viewed on acandidate terminal 102, a recruiter terminal 128, or any other suitablecomputing device.

FIG. 11A depicts a flowchart illustrating an example process forcandidate pool management using an electronic recruiting managementsystem. The process begins with block 1101 in which a job requisition isopened by Organization. The requisition may be created apart from theelectronic recruiting system. For example, a job requisition may becreated and posted to the Organization's website. In block 1102 thecandidate pool for the requisition may be populated apart from theelectronic recruiting system. For example, candidates may submitrésumés/CVs via email and postal mail, and Organization may collectthose résumés/CVs and scan and/or manually enter them intoOrganization's applicant tracking system (ATS).

In block 1103, Organization decides to integrate their applicanttracking system with the electronic recruiting system described herein.Accordingly, the requisition and information about the existingcandidate pool is transferred into the electronic recruiting system. Inblock 1104, the existing candidate pool and requisition are analyzed todetermine a necessary size of the candidate pool in order to have acertain probability that a suitable candidate will be found and hired.This analysis may be based, for example, on recruiting and hiringinformation collected from Organization, other organizations, and/or thepertinent industry in general. In block 1105, if the existing candidatepool is of the necessary size, then the process returns to block 1104.In this manner, the candidate pool may be continually and/orperiodically monitored such that candidates can be added when newcandidates meeting requirements are input to the electronic recruitingsystem and such that candidates who are no longer available for theposition can be removed from the pool.

Returning to block 1105, if the existing candidate pool is not of thenecessary size, then the process proceeds to block 1106. In block 1106,the parameters of the requisition (e.g., salary, location,qualifications, etc.) are used to search for matching candidate profilesin the electronic recruiting system. Where such requirements result in alist of candidates that is more than is needed to fill the candidatepool to then necessary size, the list of candidates may be further pareddown based on compatibility scores (e.g., based on workplace culture)between the candidates and Organization. In block 1107, the candidatesdiscovered in the search of block 1106 are recommended for addition tothe candidate pool. The administrator in charge of the requisition maybe enabled to accept or reject the recommended candidates individually,in groups, and/or as a whole. After block 1107, the process returns toblock 1104.

FIG. 11B depicts a flowchart illustrating an example process forcreating a job requisition using an electronic recruiting managementsystem. The process begins with block 1110 in which creation of a newjob requisition is started in the electronic management system via thewindow described above with reference to FIG. 10I. In block 1111, theuser creating the requisition enters a requirement/qualification for therequisition. In block 1112, the value in the candidate pool size fieldis updated based on the requirement entered in block 1111. That is, ifthe requirement/qualification sets a relatively-high standard, the valuein the candidate pool size field is likely to decrease, whereas aqualification setting a low standard may be unlikely to affect thecandidate pool size.

In block 1113, it is determined whether all requirements/qualificationsfor the requisition have been entered. If not, the process returns toblock 1111. If so, the process advances to block 1114 where it isdetermined whether the candidate pool size is big enough to ensure, witha desired probability, that a suitable candidate will be found. If thepool size is not big enough, then, in block 111, the electronicrecruiting system analyzes the qualifications/requirements and generatessuggested changes to the requirements that will get the candidate poolup to the necessary size. The user can accept one or more of thesuggested changes and/or can reject them to accept the smaller candidatepool size. In block 1116, creation of the job requisition is complete.

FIG. 12 depicts a flowchart illustrating an example process for matchingcandidate and entities via an electronic recruiting management system.For ease and clarity of description, the process of FIG. 12 is describedusing two candidates and two organizations. The process, however, isapplicable to any number of candidates and any number of organizations.The process begins with block 1201 in which each of Organization A andOrganization B register with the electronic recruiting system. In block1202, administrators of Organization A and Organization B create theirrespective profiles in the electronic recruiting system (e.g., usingwindow similar to the windows of FIGS. 8D and 9C). In block 1203,employees of Organization A and employees of Organization B fill outquestionnaires regarding their personalities, preferences, and/orworkplace culture.

In block 1204, Candidate X and Candidate Y register with the electronicrecruiting system. In block 1205, Candidates X and Y create theirrespective profiles in the electronic recruiting system (e.g., using thewindow of FIG. 8D). In block 1206, Candidates X and Y fill outquestionnaires regarding their personalities and/or workplace culturepreferences. In block 1207 compatibility scores S_(AX) (compatibilitybetween A and X), S_(AY) (compatibility between A and Y), S_(BX)(compatibility between B and X), and S_(BY) (compatibility between A andX) are generated. The compatibility scores may be generated based onOrganization A's profile, Organization B's profile, Candidate X'sprofile, Candidate Y's profile, the questionnaire responses ofOrganization A's employees, the questionnaire responses of OrganizationB's employees, Candidate X's responses to the questionnaire, and/orCandidate Y's responses to the questionnaire.

In block 1208, for each compatibility score S_(mn), that is greater thana determined threshold, the electronic recruiting system may recommendCandidate m to Organization n and/or recommend Organization n toCandidate m.

FIG. 13 depicts a flowchart illustrating an example process forcandidate recommendations via an electronic recruiting managementsystem. The process begins with block 1301 in which the electronicrecruiting system searches the requisitions of organizations that aresubscribed to Candidate A and the requisitions of organizations to whichCandidate A is subscribed. For purposes of description, it is assumedOrganization X is among such organizations. In block 1302, candidateswho are subscribed to Candidate A and candidates to whom Candidate A issubscribed are searched for candidates who match the requisition(s)discovered in block 1301. For purposes of description, it is assumedCandidate B is among such candidates. In block 1304, the search of block1303 reveals that Candidate B is a good fit for an open requisition ofOrganization X. In block 1304, Candidate A is prompted as to whethers/he would like to recommend Candidate B for the position withOrganization X. If Candidate A clicks or taps “yes,” then, in block1305, Candidate B is recommended to Organization X and visa-versa.

FIG. 14 depicts a flowchart illustrating an example process forcandidate relationship management via an electronic recruitingmanagement system. In block 1401, Candidate A interviews for a positionwith Organization X, receives a favorable evaluation, but ultimately isnot chosen for the position. In block 1402, Candidate A's information(e.g., résumé/CV, interviewer assessments, etc.) is stored inOrganization X's applicant tracking system (ATS), which is integratedwith the electronic recruiting system. In block 1403, the electronicsystem periodically and/or occasionally sends messages to (or prompts arecruiter to send messages to) Candidate A to keep Candidate A informedas to the activities of Organization X and/or to gauge whether CandidateA is still available and/or interested in a position with OrganizationX. For example, such messages may prompt Candidate A to reply if s/he isstill available and/or interested. Upon receiving such a reply, theelectronic recruiting system may automatically parse the reply andupdate Candidate A's status in the ATS. Additionally or alternatively,such messages may include questionnaires and/or fields via whichCandidate A can update his/her information and such information can beautomatically parsed and updated in the ATS upon receiving the reply.Such messages may be via the candidate's profile in the electronicrecruiting system and/or via conventional email. Where the candidate hasa profile in the electronic recruiting system, changes s/he makes toher/his profile may automatically be updated in Organization X's ATS.The updated information may be used to continually compare Candidate Aagainst Organization X's open requisitions, as such requisitions areopened.

FIG. 15 depicts an example recruiting management system that housesapplicant tracking systems for multiple organizations. Shown in FIG. 15are Organization X's enterprise network 1501, Organization Y'senterprise network 1505, and a network 1503 of a recruiting serviceprovider. Each of the networks 1501, 1503, and 1505 may compriseend-systems (e.g., servers, desktops, laptops, tablets, smartphones) andnetwork “plumbing” (e.g., routers, switches, cabling, fiber, etc.). Thenetwork 1503 may comprise one or more servers 1511.

The server(s) 1511 may comprise: a processing circuit 1507 that may besimilar to the processing circuit 120 described above with reference toFIG. 1; a networking circuit 1508 that may be similar to the networkingcircuit 118 described above with reference to FIG. 1, a memory 1509circuit that may be similar to the memory circuit 122 described abovewith reference to FIG. 1; server application 1510 which may be similarto the server application 126 described above with reference to FIG. 1;and applicant tracking system (ATS) front-ends 1506, each of which maybe similar to the database application 124 described above withreference to FIG. 1.

Each of the ATS front-ends may enable access to a particularorganization's recruiting data. The data of different organizations(stored, for example, in memory 1509) may be kept securely separated tocomply with privacy policies/regulations. Data may, however, be sharedamong organizations and/or shared with an organization-agnosticcentralized repository (which may be in memory 1509) after havingsensitive and/or private data stripped in compliance with applicableprivacy policies/regulations.

FIG. 16 depicts a flowchart illustrating an example process forprojecting recruiting-related information using an electronic recruitingmanagement system. The process begins with recruiting data of multipleorganizations' ATSs being stored in the electronic recruiting system(e.g., in memory 1509). In block 1602, identifying, private, and/orother sensitive information about the candidates in the variousorganization's ATSs is removed and the resulting privacy-cleanedinformation is stored in the electronic recruiting system (forming an“aggregate” or “cross-organizational” ATS). The information stored inthe aggregate ATS may be analyzed by the electronic recruiting system todetermine various recruiting metrics. Examples of such metrics include:number of positions filled, number of positions projected to be filledin a future time frame, candidate pool sizes used for filling pastpositions, current candidate pool sizes, current salaries, and projectedsalaries for some future time frame. The various metrics calculated fromthe information in the aggregate ATS may be categorized such as by, forexample, industry, geographic region, experience level, salary range,college major, and/or school. In block 1606, the information in theaggregate ATS and/or the metrics generate from such information may beused for generating recruiting-related projections or guidelines suchas, for example: salaries that should be paid/offered to remaincompetitive, necessary candidate pool sizes for filling positions, whichcollege majors to fund, which college majors to increase enrollment,etc.

FIG. 17 depicts a flowchart illustrating an example process for matchingcandidates and requisitions over multiple entities. The process beginswith block 1604 in which multiple organizations' ATSs are stored in theelectronic recruiting system (e.g., in memory 1509). In block 1605,Candidate A creates a profile in the electronic recruiting system (e.g.,by having his information scanned in at an event). In block 1606, theinformation from Candidate A's profile is copied to each organization'sATS. In block 1607, Candidate A is assessed for compatibility withmultiple open requisitions across multiple ones of the organizations.

In block 1608, Candidate A is notified of requisitions for which hemeets the requirements. Such a notification of block 1608 mayadditionally (or alternatively) comprise a score indicating CandidateA's compatibility with the associated organization.

For requisitions that are open for Candidate A to submit an application,Candidate A may be provided with an interface element via which s/he canapply for the requisitions, as, for example, described above withreference to FIG. 8E.

The notification may additionally (or alternatively) compriseinformation about how Candidate A may be connected to the associatedorganization in the electronic recruiting system. For example, CandidateA may be notified of a chain of one or more candidate and/ororganization subscriptions and/or past interactions that ultimately leadto the associated organization and/or one of its recruiters. Candidate Amay then attempt to seek recommendations for the requisition from one ormore of the persons or organizations along that chain. Such informationmay be useful to Candidate A where one or more of the requisitions are“invite only” (e.g., only to candidates who have been recommended bysomeone sufficiently connected to the organization). For example,Candidate A may be notified that s/he meets the requirements forposition Z with Organization X, that Candidate A is a good cultural fitfor Organization X, that Candidate A recently interacted with CandidateB at a recruiting event and that Candidate B is subscribed to byOrganization X. Accordingly, Candidate A may try to cultivate his/herrelationship with Candidate B in an attempt to get Candidate B torecommend Candidate A to Organization X via the electronic recruitingsystem.

In block 1609, the organization(s) for which Candidate A was determinedto meet the requirements for an open requisition in 1607 may be notifiedof Candidate A's fit for the position and may be notified of a chain ofsubscriptions and/or interactions that lead to Candidate A.

Accordingly, the present method and/or system may be realized inhardware, software, or a combination of hardware and software. Thepresent method and/or system may be realized in a centralized fashion inat least one computing system, or in a distributed fashion wheredifferent elements are spread across several interconnected computingsystems. Any kind of computing system or other apparatus adapted forcarrying out the methods described herein is suited. A typicalcombination of hardware and software may be a general-purpose computingsystem with a program or other code that, when being loaded andexecuted, interface elements the computing system such that it carriesout the methods described herein.

The present method and/or system may also be embedded in amachine-readable, computer program product, which comprises all thefeatures enabling the implementation of the methods described herein,and which when loaded in a computer system is able to carry out thesemethods. Computer program in the present context means any expression,in any language, code or notation, of a set of instructions intended tocause a system having an information processing capability to perform aparticular function either directly or after either or both of thefollowing: a) conversion to another language, code or notation; b)reproduction in a different material form. The computer program productmay be provided, for example, on optical and/or magnetic storage and/ormay be downloadable via network such as the Internet.

While the present method and/or system has been described with referenceto certain implementations, it will be understood by those skilled inthe art that various changes may be made and equivalents may besubstituted without departing from the scope of the present methodand/or system. In addition, many modifications may be made to adapt aparticular situation or material to the teachings of the presentdisclosure without departing from its scope. Therefore, it is intendedthat the present method and/or system not be limited to the particularimplementations disclosed, but that the present method and/or systemwill include all implementations falling within the scope of theappended claims.

What is claimed is:
 1. A method comprising: storing, in an electronicmemory of a computing system, a profile of a candidate, wherein saidprofile includes an employment-related information of said candidate;associating, in said electronic memory of said computing system, anelectronically-readable identifier with said candidate profile; reading,via an electronic reader of said computing system, saidelectronically-readable identifier from an article presented to saidcomputing system; locating said profile of said candidate in saidelectronic memory based on said read-in electronically-readableidentifier; retrieving said employment-related information of saidcandidate from said located profile; and presenting saidemployment-related information via a display of said computing system.2. The method of claim 1, comprising generating, in said computingsystem, a form for assessing said candidate.
 3. The method of claim 2,comprising presenting, via said display, said form for completion by auser of said computing system.
 4. The method of claim 3, comprising:retrieving information from said located profile; and populating atleast a portion of said form using said information retrieved from saidlocated profile.
 5. The method of claim 4, wherein said form comprises:one or more interview questions specifically selected for a particularrecruiting event based on characteristics of the recruiting event; andone or more fields for input of responses to said one or more interviewquestions provided by said candidate during an interview.
 6. The methodof claim 2, comprising making said form accessible to a plurality ofrecruiters via a network interface of said computing system.
 7. Themethod of claim 6, wherein access to said form is restricted based onpermission levels assigned to said recruiters.
 8. The method of claim 1,wherein said electronically-readable identifier is a quick response (QR)code.
 9. The method of claim 8, wherein: said article is anidentification badge generated for a recruiting event; said reader is anoptical reader; and said identification badge is presented by saidcandidate while in attendance at said recruiting event.
 10. The methodof claim 1, wherein: said profile of said candidate includes a pluralityof résumés or curriculum vitae; and which of said plurality of résumésor curriculum vitae is selected as said employment-related informationfor said presenting is determined based on one or more of: time of saidpresenting; a recruiter associated with said computing system; and anorganization associated with said computing system.
 11. The method ofclaim 1, comprising: presenting, via said display, an interface forassigning a priority level to said candidate; and associating, in saidmemory, said candidate with a priority level assigned to said candidate.12. The method of claim 1, comprising presenting, via said display, apriority level assigned to said candidate by a recruiter.
 13. The methodof claim 1, comprising: presenting, via said display, an interface for auser of said computing system to input notes about said candidate; andassociating, in said memory, said notes with said candidate.
 14. Themethod of claim 1, wherein: said processor and said memory reside in oneor more servers of said computing system; and said reader and saiddisplay reside in a mobile terminal of said computing system.
 15. Themethod of claim 1, wherein said processor, said memory, said reader andsaid display reside in a mobile terminal of said computing system. 16.The method of claim 1, comprising presenting, via said display, a listof upcoming recruiting events associated with a user of said computingsystem.
 17. The method of claim 16, comprising presenting, via saiddisplay, an interface for inviting recruiters to attend a selected oneof said recruiting events.
 18. The method of claim 1, comprisingpresenting, via said display: a list of candidates registered to attenda particular recruiting event; and an interface element for sorting saidlist of candidates registered to attend said particular recruitingevent.
 19. A system comprising: a computing system comprising aprocessor, memory, a reader, and a display, said computing systemconfigured to: store, in said memory, a profile of a candidate, whereinsaid profile includes an employment-related information of saidcandidate; associate, in said memory, a electronically-readableidentifier with said candidate profile; read, via said reader, saidelectronically-readable identifier from an article presented to saidcomputing system; locate said profile of said candidate in said memorybased on said read-in electronically-readable identifier; retrieve saidemployment-related information of said candidate from said locatedprofile; and present said employment-related information via saiddisplay.
 20. A computer program product having code stored thereon that,when executed by a computing system, causes the computing system to:store, in memory of said computing system, a profile of a candidate,wherein said profile includes an employment-related information of saidcandidate; associate, in said memory, a electronically-readableidentifier with said candidate profile; read, via a reader of saidcomputing system, said electronically-readable identifier from anarticle presented to said computing system; locate said profile of saidcandidate in said memory based on said read-in electronically-readableidentifier; retrieve said employment-related information of saidcandidate from said located profile; and present said employment-relatedinformation via a display of said computing system.